Verify AI-generated content by re-hashing and comparing to the stored provenance record.
AI agents call dual_provenance_verify to retrieve information from DUAL MCP Server 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 against stored records, which is purely informational and read-based. It has no side effects, cannot modify data, and presents minimal risk if misused—at worst, an agent might verify false claims, but the tool itself cannot alter state or commit resources.
From the tool's definition The tool description states it 'Verify[ies] AI-generated content by re-hashing and comparing to the stored provenance record.' This is a read-only operation: it retrieves and compares data without modifying, creating, deleting, or executing external…
Attacks that exploit this kind of access
Verify AI-generated content by re-hashing and comparing to the stored provenance record. It is categorised as a Read tool in the DUAL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DUAL MCP Server MCP server in PolicyLayer and add a rule for dual_provenance_verify: 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 DUAL MCP Server. Nothing to install.
dual_provenance_verify 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 dual_provenance_verify 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 dual_provenance_verify. 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.
dual_provenance_verify is provided by the DUAL MCP Server MCP server (ro-ro-b/dual-mcp-server). 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 →