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

save_contract_signers

Save signer rows for a Sanka Contract draft.

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-signers.md

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 save_contract_signers is rated Medium

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.

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.

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.