New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

save_contract_recipients

Replace the complete signer and CC recipient lists for a draft Sanka Contract. Preserve signer_id when correcting an existing signer. CC recipients are non-signers and receive separate PDF copy emails.

SERVERSanka MCP Server SOURCEsankahq/sanka-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sankahq-sanka-mcp/save-contract-recipients.md

What save_contract_recipients does on Sanka MCP Server

AI agents use save_contract_recipients 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 save_contract_recipients is rated Medium

This is a Write operation because it creates or modifies data reversibly—updating contract recipient metadata. The severity is medium because misuse could redirect contract documents to unintended recipients, potentially exposing sensitive contract terms or disrupting legitimate business workflows, but the action is reversible (recipients can be corrected again) and limited to metadata rather than financial…

From the tool's definition The tool 'save_contract_recipients' modifies recipient lists for a contract by replacing 'the complete signer and CC recipient lists for a draft Sanka Contract.' The verb 'replace' and action of updating recipient configurations indicates data modification…

Questions about save_contract_recipients

What does the save_contract_recipients tool do? +

Replace the complete signer and CC recipient lists for a draft Sanka Contract. Preserve signer_id when correcting an existing signer. CC recipients are non-signers and receive separate PDF copy emails. 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_recipients? +

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

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

Can I rate-limit save_contract_recipients? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sanka MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.