update_contract_document · AdButler MCP: Risk & Policy

WHAT IT DOES

What update_contract_document does on AdButler

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

PARAMETERS

Parameter	Type	Required	Description
`id`	number	Yes	Document ID
`name`	string	—	Document name
`contract_id`	number	Yes	Contract ID

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why update_contract_document needs a policy

The tool modifies contract documents reversibly—updates can typically be undone or versioned. This is a Write operation, not Execute (no code/command execution), Destructive (reversible), or Financial (no direct money movement, though contracts may have financial implications).

From the tool's definition Tool name 'update_contract_document' and description 'Update an existing contract document' indicate modification of existing data (Write category).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_contract_document Rate-limited

update_contract_document 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_document": {
      "limits": [
        {
          "counter": "update_contract_document_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 AdButler, so you can run agents against it safely.

FAQ

Questions about update_contract_document

What does the update_contract_document tool do? +

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

What parameters does update_contract_document accept? +

update_contract_document accepts 3 parameters: id, name, contract_id. Required: id, contract_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_contract_document? +

Register the AdButler MCP server in PolicyLayer and add a rule for update_contract_document: 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 AdButler. Nothing to install.

What risk level is update_contract_document? +

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

Can I rate-limit update_contract_document? +

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

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

update_contract_document is provided by the AdButler MCP server (adbutler/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.