get_verification_provider_capabilities

Describe a local verification provider

Server Todos @hasna/todos
Category Read
Risk class Low
Parameters 00 required

What get_verification_provider_capabilities does on Todos

AI agents call get_verification_provider_capabilities to retrieve information from Todos without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_verification_provider_capabilities needs a policy

This is a read-only operation that retrieves descriptive information about a verification provider. It has no side effects, does not create, modify, or delete data, and does not execute code or trigger financial transactions. The verb 'describe' and 'get' are consistent with information retrieval. Severity is low as misuse would only expose information about provider capabilities without enabling actual harm.

From the tool's definition Tool name 'get_verification_provider_capabilities' and description 'Describe a local verification provider' indicate a retrieval operation that queries capabilities of a verification provider without modifying data or triggering external actions.

Questions about get_verification_provider_capabilities

What does the get_verification_provider_capabilities tool do? +

Describe a local verification provider. It is categorised as a Read tool in the Todos MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_verification_provider_capabilities? +

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

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

Can I rate-limit get_verification_provider_capabilities? +

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

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

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

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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.