AI agents call verify_bundle to retrieve information from Satsignal without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
verify_bundle performs verification/lookup of blockchain-anchored hashes, which is a read operation. Deprecated status and fail-closed behavior eliminate execution risk. The incomplete description lowers confidence slightly, but the verification intent and sibling tool context (verify_file_against_bundle, verify_disclosure) indicate this is a querying/validation tool with no side effects or destructive capability.
From the tool's definition Tool is marked DEPRECATED and FAIL-CLOSED; description is truncated/incomplete ('this name silently produced'), indicating the tool is non-functional or informative-only.
Attacks that exploit this kind of access
DEPRECATED + FAIL-CLOSED — this name silently produced. It is categorised as a Read tool in the Satsignal MCP Server, which means it retrieves data without modifying state.
Register the Satsignal MCP server in PolicyLayer and add a rule for verify_bundle: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Satsignal. Nothing to install.
verify_bundle is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the verify_bundle rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for verify_bundle. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
verify_bundle is provided by the Satsignal MCP server (steleet/satsignal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →