Low Risk

self_test

Verify the packaged sample receipt and sample bundle to prove the verifier works offline.

Part of the Verify MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call self_test to retrieve information from Verify 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 self_test 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.

com-scopeblind-verify-mcp.yaml
tools:
  self_test:
    rules:
      - action: allow

See the full Verify policy for all 4 tools.

Tool Name self_test
Category Read
MCP Server Verify MCP Server
Risk Level Low

Agents calling read-class tools like self_test have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the self_test tool do? +

Verify the packaged sample receipt and sample bundle to prove the verifier works offline.. It is categorised as a Read tool in the Verify MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on self_test? +

Add a rule in your Intercept YAML policy under the tools section for self_test. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Verify MCP server.

What risk level is self_test? +

self_test is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit self_test? +

Yes. Add a rate_limit block to the self_test 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.

How do I block self_test completely? +

Set action: deny in the Intercept policy for self_test. 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.

What MCP server provides self_test? +

self_test is provided by the Verify MCP server (@scopeblind/verify-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Verify

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.