delete_transaction
AI agents call delete_transaction to permanently remove resources in ntropy-mcp MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool name 'delete_transaction' strongly suggests permanent deletion of transaction data. In a banking context, this is destructive—deleted transactions cannot be recovered and affect financial records, audit trails, and account reconciliation. Even without a description, the semantic meaning of 'delete' in an API context indicates an irreversible operation.
From the tool's definition Tool name is 'delete_transaction' with no description provided. The verb 'delete' combined with the banking/transaction domain indicates irreversible removal of transaction records.
Attacks that exploit this kind of access
delete_transaction. It is categorised as a Destructive tool in the ntropy-mcp MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ntropy-mcp MCP Server 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 ntropy-mcp MCP Server. 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 ntropy-mcp MCP Server MCP server (ntropy-network/ntropy-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 →