Verify a Shuka proof token and get details about the attestation. Use this when you: - Receive a proof token and need to confirm it's valid - Want to check the trust score before proceeding - Need to see what was attested and when - Want to verify claims before acting on data Proof tokens look ...
Part of the Shukashake MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call verify_proof to retrieve information from Shukashake without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though verify_proof only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
verify_proof:
rules:
- action: allowSee the full Shukashake policy for all 3 tools.
Agents calling read-class tools like verify_proof have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Verify a Shuka proof token and get details about the attestation. Use this when you: - Receive a proof token and need to confirm it's valid - Want to check the trust score before proceeding - Need to see what was attested and when - Want to verify claims before acting on data Proof tokens look like: shk_v1.YWJjMTIz.a1b2c3 or ENV-xxx. It is categorised as a Read tool in the Shukashake MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for verify_proof. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Shukashake MCP server.
verify_proof 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_proof rule in your Intercept 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 Intercept policy for verify_proof. 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_proof is provided by the Shukashake MCP server (@shukashake/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept