LeashIndex Get the report

Index / other

GHOSBC Safety Gate

io-github-misfitmediahouse-ghosbc-safety-gate declares 9 capabilities across 9 tools, with 3 critical issues.

55/100 exposureElevated

Manifest recorded 2026-10-11 from tools/list on https://cibcxqrqiqvzpardbdrw.supabase.co/functions/v1/ghosbc-safety-gate-mcp, published in the official MCP registry as io.github.MisfitMEdiAhouse/ghosbc-safety-gate 1.5.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 9 tools

9 of 9 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 · 2 of 9 tools

2 tools are classified as irreversible and declare no limit.

critical · uncapped-spend · 1 of 9 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 9 tools

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

9 of 9 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 · 6 of 9 tools

6 tools can modify data and declare no limit.

low · uncapped-read · 1 of 9 tools

1 tool can read data and declares 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
audit_a2a_agent_cardwrite assumed
audit_shopify_agentic_storefrontwrite assumed
audit_mcp_dependencywrite assumed
screen_agent_requestwrite inferred
screen_mcp_tool_definitionwrite assumed
screen_consequential_actionwrite assumed
sanitize_agent_payloadsend inferred
validate_agent_responseread inferred
buy_policy_checkspay 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.