Revoke stacking delegation via the PoX contract.
AI agents use stx_revoke_delegation to commit financial operations through Bitcoin wallet MCP server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool modifies a financial/staking arrangement on the Stacks blockchain by revoking a stacking delegation through the PoX (Proof of Transfer) contract. Revoking a delegation affects committed financial positions (stacked STX tokens), constituting a financial operation. It is also potentially irreversible in the current stacking cycle, making misuse high severity.
From the tool's definition Revoke stacking delegation via the PoX contract
Attacks that exploit this kind of access
Revoke stacking delegation via the PoX contract. It is categorised as a Financial tool in the Bitcoin wallet MCP server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Bitcoin wallet MCP server MCP server in PolicyLayer and add a rule for stx_revoke_delegation: 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 Bitcoin wallet MCP server. Nothing to install.
stx_revoke_delegation 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 stx_revoke_delegation 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 stx_revoke_delegation. 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.
stx_revoke_delegation is provided by the Bitcoin wallet MCP server MCP server (markmhendrickson/mcp-server-bitcoin). 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 →