LeashIndex Get the report

Index / devtools

Cloud for Bots

com-botrecipe-cloudforbots declares 48 capabilities across 48 tools, with 2 critical issues.

93/100 exposureHigh exposure

Manifest recorded 2026-10-16 from tools/list on https://cloudforbots.com/mcp, published in the official MCP registry as com.botrecipe/cloudforbots 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 48 tools

48 of 48 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 · 3 of 48 tools

3 tools are classified as irreversible and declare no limit.

high · no-expiry · All 48 tools

48 of 48 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 48 tools

48 of 48 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 · 30 of 48 tools

30 tools can modify data and declare no limit.

low · uncapped-read · 15 of 48 tools

15 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
loop_check_stepwrite assumed
loop_loop_statusread inferred
loop_weekly_reportwrite assumed
loop_usage_and_upgraderead inferred
memory_save_checkpointwrite assumed
memory_resumewrite assumed
memory_list_checkpointsread inferred
memory_weekly_reportwrite assumed
memory_usage_and_upgraderead inferred
budget_open_budgetwrite assumed
budget_reservewrite assumed
budget_recordread inferred
budget_weekly_reportwrite assumed
budget_budget_statusread inferred
budget_usage_and_upgraderead inferred
approve_check_actionwrite inferred
approve_get_decisionread inferred
approve_set_ruleswrite inferred
approve_get_rulesread inferred
approve_weekly_reportwrite inferred
approve_usage_and_upgradewrite inferred
wake_schedule_wakewrite assumed
wake_check_wakeswrite assumed
wake_cancel_wakedelete inferred
wake_usage_and_upgraderead inferred
library_searchread inferred
library_getread inferred
library_installwrite assumed
library_publishsend inferred
library_rateread inferred
library_reportwrite assumed
vaultwrite assumed
handoffwrite assumed
replaywrite assumed
secretswrite assumed
fetchread inferred
queuewrite assumed
cronwrite assumed
browserwrite assumed
lockwrite assumed
ratewrite assumed
inboxwrite assumed
topicsend inferred
aiwrite assumed
ledgerread inferred
sandboxwrite assumed
storewrite assumed
reportwrite assumed
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.