LeashIndex Get the report

Index / devtools

Boat House

com-boathousecloud-boathouse declares 41 capabilities across 41 tools, with 3 critical issues.

94/100 exposureHigh exposure

Manifest recorded 2026-10-11 from tools/list on https://mcp.boathousecloud.com/mcp, published in the official MCP registry as com.boathousecloud/boathouse 1.0.0. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 41 tools

41 of 41 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · irreversible-uncapped · 5 of 41 tools

5 tools are classified as irreversible and declare no limit.

critical · uncapped-spend · 1 of 41 tools

1 tool is classified as moving money and declares no dollar limit. A cap on the number of payments does not bound their amount.

high · no-expiry · All 41 tools

41 of 41 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 41 tools

41 of 41 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 27 of 41 tools

27 tools can modify data and declare no limit.

low · uncapped-read · 9 of 41 tools

9 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
whoamiwrite assumed
list_toolsread inferred
get_toolread inferred
deploywrite inferred
pullread inferred
logswrite assumed
releaseswrite assumed
rollbackwrite assumed
restartwrite assumed
sharesend inferred
unsharewrite assumed
request_accesswrite inferred
access_requestswrite inferred
allow_requestwrite inferred
set_accesswrite inferred
secrets_listread inferred
secrets_setwrite inferred
secrets_deletedelete inferred
users_listread inferred
users_addwrite inferred
users_invitewrite assumed
users_removedelete inferred
domains_listread inferred
domain_checkwrite assumed
domain_buypay inferred
domain_renewalsread inferred
domain_renewal_setwrite inferred
domain_attachwrite assumed
domain_pointread inferred
domain_primarywrite assumed
domain_dnswrite assumed
domain_repointwrite inferred
domain_detachwrite assumed
usageread inferred
capacitywrite assumed
billingwrite assumed
priceswrite assumed
referralwrite assumed
topupwrite inferred
card_linkwrite assumed
delete_tooldelete inferred
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.