Execute a state-changing contract call
AI agents invoke stbl_write_contract to trigger actions in Stability 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.
This tool executes state-changing operations on a blockchain smart contract. While it's not purely destructive (changes may be reversible depending on contract logic), it runs arbitrary contract code that can modify blockchain state, transfer tokens, or trigger complex on-chain operations.
From the tool's definition "Execute a state-changing contract call"
Attacks that exploit this kind of access
Execute a state-changing contract call. It is categorised as a Execute tool in the Stability MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Stability MCP Server MCP server in PolicyLayer and add a rule for stbl_write_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 Stability MCP Server. Nothing to install.
stbl_write_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 stbl_write_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 stbl_write_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.
stbl_write_contract is provided by the Stability MCP Server MCP server (nuljui/stbl-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 →