update-contract · Openfort MCP Server MCP: Risk & Policy

WHAT IT DOES

What update-contract does on Openfort MCP Server

AI agents use update-contract to create or update resources in Openfort MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Openfort MCP Server environment.

WHY IT NEEDS A POLICY

Why update-contract needs a policy

This tool modifies data (contract details/configuration) but does not permanently delete it. The change is reversible through subsequent updates. Given that contracts in a Web3/wallet infrastructure context often govern critical transaction logic and policies, unauthorized updates could redirect funds or change authorization rules, making this a high-severity Write operation.

From the tool's definition Tool name is 'update-contract' with description 'Update an existing contract'. The verb 'update' indicates modification of existing data (a contract configuration or smart contract parameters) in a reversible manner.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update-contract Rate-limited

update-contract stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update-contract": {
      "limits": [
        {
          "counter": "update-contract_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about update-contract

What does the update-contract tool do? +

Update an existing contract. It is categorised as a Write tool in the Openfort MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update-contract? +

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

What risk level is update-contract? +

update-contract is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update-contract? +

Yes. Add a rate_limit block to the update-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 update-contract completely? +

Set action: deny in the PolicyLayer policy for update-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 update-contract? +

update-contract is provided by the Openfort MCP Server MCP server (openfort-xyz/-deprecated-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.