schedule_contract_request
Schedule a Sanka Contract signature request for later sending.
This record as markdown: /tools/sankahq-sanka-mcp/schedule-contract-request.md
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 schedule_contract_request is rated Medium
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
The rule that runs schedule_contract_request safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For schedule_contract_request, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Sanka MCP Server, apply this rule, and every schedule_contract_request call is checked against it from then on.
Questions about schedule_contract_request
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.
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.
schedule_contract_request is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
More on Sanka MCP Server, and thousands of servers like it.
This server
Across the catalogue