schedule_contract_request · Sanka MCP Server MCP

WHAT IT DOES

What schedule_contract_request does on Sanka MCP Server

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

This tool creates a new data record (a scheduled contract request) in the system, which is a Write operation. It does not delete data (not Destructive), execute arbitrary code (not Execute), or move money directly (not Financial), though it may be part of a financial workflow.

From the tool's definition schedule_contract_request schedules (creates/queues) a contract signature request for later sending. The description indicates this tool creates a new scheduled request object that will trigger a future action.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

schedule_contract_request Rate-limited

schedule_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": {
    "schedule_contract_request": {
      "limits": [
        {
          "counter": "schedule_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 schedule_contract_request

What does the schedule_contract_request tool do? +

Schedule a Sanka Contract signature request for later 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 schedule_contract_request? +

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

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

Can I rate-limit schedule_contract_request? +

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

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

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