Create a deal in Sanka or a connected CRM.
AI agents use create_deal 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.
This tool creates deal records in a CRM system, which is a reversible write operation. It has high severity due to potential business impact (deals represent sales commitments and revenue projections), but it is not Destructive since creation can be undone, not Financial since it doesn't move money directly, and not Execute since it performs a structured API operation rather than arbitrary code execution.
From the tool's definition Tool name 'create_deal' and description 'Create a deal in Sanka or a connected CRM' indicate this operation creates new data records.
Attacks that exploit this kind of access
Create a deal in Sanka or a connected CRM. 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 create_deal: 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.
create_deal 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 create_deal 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 create_deal. 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.
create_deal 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →