write_contract · SEI MCP Server V2 MCP: Risk & Policy

WHAT IT DOES

What write_contract does on SEI MCP Server V2

AI agents invoke write_contract to trigger actions in SEI MCP Server V2. 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.

WHY IT NEEDS A POLICY

Why write_contract needs a policy

This tool executes arbitrary state-changing function calls on smart contracts. While named 'write', it is effectively an Execute-category tool because it triggers external blockchain operations whose effects are entirely determined by the arguments (contract address, function, parameters).

From the tool's definition "Write data to a smart contract by calling a state-changing function"

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

write_contract Rate-limited

write_contract stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "write_contract": {
      "limits": [
        {
          "counter": "write_contract_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches SEI MCP Server V2, so you can run agents against it safely.

FAQ

Questions about write_contract

What does the write_contract tool do? +

Write data to a smart contract by calling a state-changing function. It is categorised as a Execute tool in the SEI MCP Server V2 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on write_contract? +

Register the SEI MCP Server V2 MCP server in PolicyLayer and add a rule for 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 SEI MCP Server V2. Nothing to install.

What risk level is write_contract? +

write_contract is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit write_contract? +

Yes. Add a rate_limit block to the 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.

How do I block write_contract completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides write_contract? +

write_contract is provided by the SEI MCP Server V2 MCP server (testinguser1111111/sei-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.