AI agents call prmaat_verify_receipt to retrieve information from Prmaat without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Verification is a read-only operation that inspects and validates cryptographic signatures or proofs. It has no side effects, does not execute code or external operations, does not modify data, and does not move money. The tool only returns validation results based on input receipt data, consistent with the 'Read' category for data retrieval and inspection operations.
From the tool's definition Tool name 'prmaat_verify_receipt' and description indicate verification of a Verifiable Execution Receipt (JWS Compact, JCS canonicalization) — a cryptographic validation operation that examines/reads data without modifying, creating, executing, or deleting…
Attacks that exploit this kind of access
Verify a v0.2 Verifiable Execution Receipt (JWS Compact, JCS canonicalization,. It is categorised as a Read tool in the Prmaat MCP Server, which means it retrieves data without modifying state.
Register the Prmaat MCP server in PolicyLayer and add a rule for prmaat_verify_receipt: 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 Prmaat. Nothing to install.
prmaat_verify_receipt 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 prmaat_verify_receipt 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 prmaat_verify_receipt. 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.
prmaat_verify_receipt is provided by the Prmaat MCP server (prmaat/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 →