Add a bot to a pool, and optionally make a payment as that bot through the shared treasury.
AI agents use paybot_pool_allocate to commit financial operations through PayBot MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool can trigger financial transactions (payments) through a shared treasury, making it Financial category. The ability to move funds from a shared treasury as an arbitrary bot makes this critical severity — misuse could drain pooled funds or commit unauthorized payments at scale.
From the tool's definition 'Add a bot to a pool, and optionally make a payment as that bot through the shared treasury'
Attacks that exploit this kind of access
Add a bot to a pool, and optionally make a payment as that bot through the shared treasury. It is categorised as a Financial tool in the PayBot MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the PayBot MCP Server MCP server in PolicyLayer and add a rule for paybot_pool_allocate: 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_allocate is a Financial 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_allocate 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_allocate. 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_allocate 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 →