Call a public Clarity smart contract function.
AI agents invoke stx_call_contract to trigger actions in Bitcoin wallet MCP server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Executing a smart contract function on-chain triggers external operations with real blockchain effects. While some contract calls are read-only, 'public' Clarity functions can transfer tokens, modify state, or invoke other contracts irreversibly.
From the tool's definition Call a public Clarity smart contract function
Attacks that exploit this kind of access
Call a public Clarity smart contract function. It is categorised as a Execute tool in the Bitcoin wallet MCP server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Bitcoin wallet MCP server MCP server in PolicyLayer and add a rule for stx_call_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_call_contract is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the stx_call_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_call_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_call_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 →