Cancel a Sanka Buy request before downstream purchasing is complete.
AI agents call cancel_buy_request to permanently remove resources in Sanka MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
While not strictly a deletion of data, canceling a buy request irreversibly terminates a financial transaction in progress. This prevents downstream purchasing from completing, which has material business consequences and cannot be easily undone. The action is more severe than a simple Write operation (which is reversible) and constitutes a Destructive action in the context of business workflows.
From the tool's definition The tool description explicitly states 'Cancel a Sanka Buy request' which terminates an existing purchasing transaction.
Attacks that exploit this kind of access
Cancel a Sanka Buy request before downstream purchasing is complete. It is categorised as a Destructive tool in the Sanka MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for cancel_buy_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.
cancel_buy_request is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cancel_buy_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 cancel_buy_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.
cancel_buy_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.
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 →