save_contract_signers · Sanka MCP Server MCP: Risk & Policy

WHAT IT DOES

What save_contract_signers does on Sanka MCP Server

AI agents use save_contract_signers 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 save_contract_signers needs a policy

This tool modifies contract signers on draft contracts, which is a reversible write operation. It is not destructive (does not delete), not financial (does not move money), and not execute (does not run arbitrary code). However, it carries high severity because misconfigured signers on contracts could have significant business consequences—wrong signers could invalidate contract execution or cause workflow failures.

From the tool's definition Tool name 'save_contract_signers' and description 'Save signer rows for a Sanka Contract draft' indicate creation/modification of contract signer data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

save_contract_signers Rate-limited

save_contract_signers 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": {
    "save_contract_signers": {
      "limits": [
        {
          "counter": "save_contract_signers_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 save_contract_signers

What does the save_contract_signers tool do? +

Save signer rows for a Sanka Contract draft. 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 save_contract_signers? +

Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for save_contract_signers: 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 save_contract_signers? +

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

Can I rate-limit save_contract_signers? +

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

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

save_contract_signers 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.