AI agents call verify_disclosure 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.
This tool performs verification and confirmation of existing disclosure data. The verb 'verify' and 'confirm' are inspection operations with no side effects—they query or validate state without creating, modifying, deleting, or executing external operations. The context (blockchain anchoring via BSV) confirms this is a read-only lookup/verification operation.
From the tool's definition Tool name 'verify_disclosure' and description 'Verify a redacted disclosure .mbnt: confirm every REVEALED leaf' indicate a verification/validation operation that reads and confirms data without modifying it.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Verify a redacted disclosure .mbnt: confirm every REVEALED leaf. 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_disclosure: 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_disclosure 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_disclosure 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_disclosure. 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_disclosure 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 →