delete_expense
AI agents call delete_expense to permanently remove resources in ExpenseTracker MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Delete operations are irreversible and constitute data destruction. Even without a description, the name 'delete_expense' clearly indicates removal of financial records. In a personal finance context, deleting expense entries removes audit trails and historical data that cannot be recovered. This qualifies as Destructive rather than Write (which is reversible).
From the tool's definition Tool named 'delete_expense' with empty description. The name alone indicates irreversible deletion of financial data. Context shows this is a personal finance management system with a persistent PostgreSQL database where expenses are stored long-term.
Attacks that exploit this kind of access
delete_expense. It is categorised as a Destructive tool in the ExpenseTracker MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ExpenseTracker MCP Server MCP server in PolicyLayer and add a rule for delete_expense: 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 ExpenseTracker MCP Server. Nothing to install.
delete_expense 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_expense 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_expense. 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_expense is provided by the ExpenseTracker MCP Server MCP server (tanishra/expense-tracker-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 →