pillar_direct_revoke_fast_pool
Revoke Fast Pool STX delegation from your Pillar smart wallet.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/pillar-direct-revoke-fast-pool.md
What pillar_direct_revoke_fast_pool does on Aibtc
AI agents call pillar_direct_revoke_fast_pool to permanently remove resources in Aibtc, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why pillar_direct_revoke_fast_pool is rated Critical
This tool revokes (cancels/withdraws) STX delegation from a smart wallet. Revocation is a destructive operation—once executed, the delegation is removed and cannot be automatically restored. While the user could re-delegate later, the current delegation state is irreversibly altered. This is more severe than Write (which is reversible) and qualifies as Destructive.
From the tool's definition Tool name and description explicitly use 'Revoke', which means to withdraw or cancel delegation. Revoking STX delegation is an irreversible action that cannot be undone without re-delegating, and results in loss of delegation benefits immediately.
Attacks that exploit this kind of access
The rule that runs pillar_direct_revoke_fast_pool safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pillar_direct_revoke_fast_pool, this is the rule to start with:
pillar_direct_revoke_fast_pool is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every pillar_direct_revoke_fast_pool call is checked against it from then on.
Questions about pillar_direct_revoke_fast_pool
Revoke Fast Pool STX delegation from your Pillar smart wallet. It is categorised as a Destructive tool in the Aibtc MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Aibtc MCP server in PolicyLayer and add a rule for pillar_direct_revoke_fast_pool: 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 Aibtc. Nothing to install.
pillar_direct_revoke_fast_pool 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 pillar_direct_revoke_fast_pool 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 pillar_direct_revoke_fast_pool. 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.
pillar_direct_revoke_fast_pool is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aibtc, and thousands of servers like it.
Across the catalogue