set_verification_provider · Todos MCP: Risk & Policy

WHAT IT DOES

What set_verification_provider does on Todos

AI agents use set_verification_provider 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 set_verification_provider needs a policy

This tool modifies configuration state by creating or updating a verification provider adapter. While it configures local-only verification (reducing cloud exposure risk), it still writes data that affects the verification system's behavior. The reversibility (can be updated or removed), localized scope, and configuration-only nature make it Write rather than Execute or Destructive.

From the tool's definition Tool description states 'Create or update an optional local verification provider adapter', explicitly indicating write operations (create/update) on provider configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_verification_provider Rate-limited

set_verification_provider 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": {
    "set_verification_provider": {
      "limits": [
        {
          "counter": "set_verification_provider_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 set_verification_provider

What does the set_verification_provider tool do? +

Create or update an optional local verification provider adapter. Providers are local-only and do not call cloud services unless the configured command does so. 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 set_verification_provider? +

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

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

Can I rate-limit set_verification_provider? +

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

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

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