Low Risk

verify_dossier

Security verification - Verify integrity (checksum) and authenticity (signature) of a dossier. Returns pass/fail with stage details.

Risk signalsAccepts file system path (path)

Part of the Ai Dossier server.

verify_dossier is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE AI DOSSIER →

Free to start. No card required.

AI agents call verify_dossier to retrieve information from Ai Dossier 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_dossier 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "verify_dossier": {}
  }
}

See the full Ai Dossier policy for all 10 tools.

Get this rule live on your own Ai Dossier server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY AI DOSSIER →

View all 10 tools →

These attack patterns abuse exactly the kind of access verify_dossier gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so verify_dossier only ever does what you allow.

SECURE AI DOSSIER →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the verify_dossier tool do? +

Security verification - Verify integrity (checksum) and authenticity (signature) of a dossier. Returns pass/fail with stage details.. It is categorised as a Read tool in the Ai Dossier MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on verify_dossier? +

Register the Ai Dossier MCP server in PolicyLayer and add a rule for verify_dossier: 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 Ai Dossier. Nothing to install.

What risk level is verify_dossier? +

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

Can I rate-limit verify_dossier? +

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

How do I block verify_dossier completely? +

Set action: deny in the PolicyLayer policy for verify_dossier. 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 verify_dossier? +

verify_dossier is provided by the Ai Dossier MCP server (@ai-dossier/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ai Dossier tool call.

Deterministic rules across all 10 Ai Dossier tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.