Remove a bot from a pool.
AI agents call paybot_pool_revoke to permanently remove resources in PayBot MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
While not a direct financial transfer, revoking/removing a bot from a payment pool is an irreversible action that disrupts the bot's participation in pooled fund management. This is more severe than Write (reversible modification) because the revocation is a destructive state change to financial infrastructure.
From the tool's definition Tool name 'paybot_pool_revoke' with description 'Remove a bot from a pool' indicates irreversible removal of a bot from a payment pool.
Attacks that exploit this kind of access
Remove a bot from a pool. It is categorised as a Destructive tool in the PayBot MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the PayBot MCP Server MCP server in PolicyLayer and add a rule for paybot_pool_revoke: 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 PayBot MCP Server. Nothing to install.
paybot_pool_revoke is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the paybot_pool_revoke 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.
Set action: deny in the PolicyLayer policy for paybot_pool_revoke. 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.
paybot_pool_revoke is provided by the PayBot MCP Server MCP server (rbkunnela/paybot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →