create_verification_evidence · Todos MCP: Risk & Policy

WHAT IT DOES

What create_verification_evidence does on Todos

AI agents use create_verification_evidence to create or update resources in Todos — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todos environment.

WHY IT NEEDS A POLICY

Why create_verification_evidence needs a policy

This tool creates and stores new verification evidence records, which are reversible modifications to the system's data. It does not execute commands or make financial transactions, nor does it delete data irreversibly. It falls under Write category as it creates structured data records.

From the tool's definition The tool name and description indicate it creates a new record ('Create a portable verification evidence record'). This is a write operation that adds data to the system (evidence records with commands, test results, CI links, and artifact references).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_verification_evidence Rate-limited

create_verification_evidence stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_verification_evidence": {
      "limits": [
        {
          "counter": "create_verification_evidence_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Todos, so you can run agents against it safely.

FAQ

Questions about create_verification_evidence

What does the create_verification_evidence tool do? +

Create a portable verification evidence record with commands, test results, CI links, and artifact refs. It is categorised as a Write tool in the Todos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_verification_evidence? +

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

What risk level is create_verification_evidence? +

create_verification_evidence is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_verification_evidence? +

Yes. Add a rate_limit block to the create_verification_evidence 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 create_verification_evidence completely? +

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

create_verification_evidence is provided by the Todos MCP server (@hasna/todos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.