Delete expense from Splitwise and remove from cache.
AI agents call splitwise_delete_expense to permanently remove resources in Splitwise MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes expense records from Splitwise, which cannot be undone. Deletion of financial records is irreversible data destruction. While the impact is limited to a single expense entry (not a mass purge), the destructive nature of removing financial transaction history justifies the Destructive category over Write.
From the tool's definition 'Delete expense from Splitwise and remove from cache' - the tool explicitly performs deletion, which irreversibly removes financial transaction data.
Attacks that exploit this kind of access
Delete expense from Splitwise and remove from cache. It is categorised as a Destructive tool in the Splitwise MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Splitwise MCP Server MCP server in PolicyLayer and add a rule for splitwise_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 Splitwise MCP Server. Nothing to install.
splitwise_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 splitwise_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 splitwise_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.
splitwise_delete_expense is provided by the Splitwise MCP Server MCP server (vishnujayvel/splitwise-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 →