run_verification_provider · Todos MCP: Risk & Policy

WHAT IT DOES

What run_verification_provider does on Todos

AI agents invoke run_verification_provider to trigger actions in Todos. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why run_verification_provider needs a policy

This tool executes external verification logic (a 'provider') which could perform arbitrary operations depending on its implementation. While not destructive by itself, the execution of external code with potential side effects on verification state qualifies as Execute.

From the tool's definition Tool name explicitly states 'run_verification_provider' and description says 'Run a local verification provider'. The verb 'run' combined with 'verification provider' indicates execution of external code/operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_verification_provider Rate-limited

run_verification_provider stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_verification_provider": {
      "limits": [
        {
          "counter": "run_verification_provider_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 run_verification_provider

What does the run_verification_provider tool do? +

Run a local verification provider and optionally record task verification evidence. It is categorised as a Execute tool in the Todos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_verification_provider? +

Register the Todos MCP server in PolicyLayer and add a rule for run_verification_provider: 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 run_verification_provider? +

run_verification_provider is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_verification_provider? +

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

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

run_verification_provider 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.