update_contract · QuickContract MCP: Risk & Policy

WHAT IT DOES

What update_contract does on QuickContract MCP

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

WHY IT NEEDS A POLICY

Why update_contract needs a policy

This tool modifies contract data in a draft state. While contracts are legally significant documents, the restriction to draft status ("Only works while status=") means changes are reversible and not yet binding. The capability to alter contract terms, names, and fields constitutes Write-category functionality.

From the tool's definition Tool description states "Update a draft contract: change filledFields, contractName, or edit individual section bodies." The term "update" combined with modification of contract content (filledFields, contractName, section bodies) indicates reversible data…

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 QuickContract MCP, so you can run agents against it safely.

FAQ

Questions about update_contract

What does the update_contract tool do? +

Update a draft contract: change filledFields, contractName, or edit individual section bodies. Only works while status=\. It is categorised as a Write tool in the QuickContract MCP 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 QuickContract 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 QuickContract MCP. 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 QuickContract MCP server (quickcontractio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.