// MCP TOOL REFERENCE

VERIFY TOOLS

4 tools from the Verify MCP Server, categorised by risk level.

READ TOOLS

explain_artifact Explain the format and top-level contents of a signed artifact without requiring a verification key. self_test Verify the packaged sample receipt and sample bundle to prove the verifier works offline. verify_bundle Verify a ScopeBlind audit bundle offline using the embedded verification keys. 2/5 verify_receipt Verify a single signed artifact or receipt using an explicit public key or any embedded public key.

// FAQ

How many tools does the Verify MCP server have? +

The Verify MCP server exposes 4 tools across 1 categories: Read.

How do I enforce policies on Verify tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Verify server.

What risk categories do Verify tools fall into? +

Verify tools are categorised as Read (4). Each category has a recommended default policy.

Enforce policies on Verify

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →