send_contract_request · Sanka MCP Server MCP: Risk & Policy

WHAT IT DOES

What send_contract_request does on Sanka MCP Server

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

This tool creates new contract signature requests or modifies existing ones by resending them. This is a Write operation because it creates/modifies data reversibly—the action can be undone (cancelled, withdrawn) and does not irreversibly delete data or commit financial obligations directly.

From the tool's definition send_contract_request is described as 'Send or resend a Sanka Contract signature request', which creates or modifies the state of a contract request (initiating or re-initiating a signature workflow).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_contract_request Rate-limited

send_contract_request 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": {
    "send_contract_request": {
      "limits": [
        {
          "counter": "send_contract_request_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 send_contract_request

What does the send_contract_request tool do? +

Send or resend a Sanka Contract signature request. 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 send_contract_request? +

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

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

Can I rate-limit send_contract_request? +

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

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

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