Deploy a Clarity smart contract to the Stacks blockchain.
AI agents use stx_deploy_contract 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.
Deploying a smart contract to a blockchain is a financial operation: it broadcasts an irreversible on-chain transaction that consumes STX tokens as fees and permanently publishes executable code. On a Bitcoin wallet server handling real assets, a misused deployment could commit funds, create malicious contracts to drain wallets, or lock tokens.
From the tool's definition Deploy a Clarity smart contract to the Stacks blockchain
Attacks that exploit this kind of access
Deploy a Clarity smart contract to the Stacks blockchain. 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_deploy_contract: 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_deploy_contract 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_deploy_contract 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_deploy_contract. 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_deploy_contract 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 →