update_contract_metadata · Sanka MCP Server MCP

WHAT IT DOES

What update_contract_metadata does on Sanka MCP Server

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

WHY IT NEEDS A POLICY

Why update_contract_metadata needs a policy

The tool creates or modifies data reversibly by updating contract draft properties (name/description). It does not execute code, delete data irreversibly, or move money. The 'high' severity reflects that contracts are legally significant documents—corrupting metadata could cause confusion or disputes—but the modification is reversible and limited to draft state before sending.

From the tool's definition Tool name contains 'update' and description states 'Update a Sanka Contract draft name or description before sending.' This explicitly modifies contract metadata.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_contract_metadata Rate-limited

update_contract_metadata 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_metadata": {
      "limits": [
        {
          "counter": "update_contract_metadata_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 Sanka MCP Server, so you can run agents against it safely.

FAQ

Questions about update_contract_metadata

What does the update_contract_metadata tool do? +

Update a Sanka Contract draft name or description before sending. It is categorised as a Write tool in the Sanka 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_metadata? +

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

What risk level is update_contract_metadata? +

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

Can I rate-limit update_contract_metadata? +

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

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

update_contract_metadata is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.