AI agents call verify_url to retrieve information from Unfakable without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs cryptographic verification and proof validation without creating, modifying, deleting, or executing arbitrary code. It queries public data and performs local computations to determine file authenticity. No state is modified, no commands are executed, and no irreversible actions occur.
From the tool's definition Tool description states it 'Fetch[es] a public document URL, compute[s] its SHA-256 fingerprint, and check[s] whether Unfakable has a Bitcoin-anchored proof.' These are all read-only operations: fetching from a public URL, computing a hash (no side effects),…
Attacks that exploit this kind of access
Fetch a public document URL, compute its SHA-256 fingerprint, and check whether Unfakable has a Bitcoin-anchored proof. Use this when the file is hosted online (e.g. a verifier handle, a public PDF link). It is categorised as a Read tool in the Unfakable MCP Server, which means it retrieves data without modifying state.
Register the Unfakable MCP server in PolicyLayer and add a rule for verify_url: 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 Unfakable. Nothing to install.
verify_url 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_url 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_url. 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_url is provided by the Unfakable MCP server (unfakable/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 →