Mark a Kaspi order as COMPLETED. WARNING: This is IRREVERSIBLE! Only use when the order has been fully delivered.
AI agents call complete_order to permanently remove resources in Kaspi Merchant — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently changes order status in a production e-commerce system with no undo capability. The description explicitly warns of irreversibility. An AI agent misusing this could mark undelivered orders as completed, causing financial disputes, customer complaints, and operational chaos.
From the tool's definition 'Mark a Kaspi order as COMPLETED. WARNING: This is IRREVERSIBLE! Only use when the order has been fully delivered.' — explicitly states irreversible operation on production order data.
Attacks that exploit this kind of access
Mark a Kaspi order as COMPLETED. WARNING: This is IRREVERSIBLE! Only use when the order has been fully delivered. It is categorised as a Destructive tool in the Kaspi Merchant MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Kaspi Merchant MCP server in PolicyLayer and add a rule for complete_order: 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 Kaspi Merchant. Nothing to install.
complete_order 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 complete_order 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 complete_order. 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.
complete_order is provided by the Kaspi Merchant MCP server (theyahia/kaspi-merchant-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 →