This record as markdown: /tools/com-zype-mcp-server/delete-transaction.md
What delete_transaction does on Zype Com
AI agents call delete_transaction to permanently remove resources in Zype Com, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
confirm | boolean | — | Set true to confirm (required in safe mode) |
transaction_id | string | Yes | The transaction ID (required) |
Parameters from the server's own tool schema.
Why delete_transaction is rated Critical
An AI agent that decides to call delete_transaction doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Zype Com is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs delete_transaction safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Zype Com, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_transaction, this is the rule to start with:
delete_transaction is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Zype Com, apply this rule, and every delete_transaction call is checked against it from then on.
Questions about delete_transaction
Delete a transaction record. It is categorised as a Destructive tool in the Zype Com MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_transaction accepts 2 parameters: confirm, transaction_id. Required: transaction_id. The full parameter table on this page comes from the server's own tool schema.
Register the Zype Com MCP server in PolicyLayer and add a rule for delete_transaction: 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 Zype Com. Nothing to install.
delete_transaction 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 delete_transaction 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 delete_transaction. 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.
delete_transaction is provided by the Zype Com MCP server (zype/zype-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Zype Com, and thousands of servers like it.
Across the catalogue