New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

remove_verification_provider

Remove a configured local verification provider.

SERVERTodos SOURCE@hasna/todos
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/todos/remove-verification-provider.md

What remove_verification_provider does on Todos

AI agents call remove_verification_provider to permanently remove resources in Todos, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why remove_verification_provider is rated Critical

Removing a configured provider is an irreversible deletion of configuration data. If the provider is removed, any tasks or workflows relying on it may break, and the configuration cannot be automatically restored. This qualifies as Destructive rather than Write.

From the tool's definition 'Remove a configured local verification provider' — permanently removes/deletes a configuration entry

Questions about remove_verification_provider

What does the remove_verification_provider tool do? +

Remove a configured local verification provider. It is categorised as a Destructive tool in the Todos MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_verification_provider? +

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

remove_verification_provider is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_verification_provider? +

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

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

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

More on Todos, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Todos's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.