Restore a deleted expense.
AI agents use splitwise_restore_expense to create or update resources in Splitwise MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Splitwise MCP Server environment.
This tool reverses a prior Destructive action (deletion) by restoring data. While it modifies state and creates/reactivates data, it is fundamentally a recovery/undo operation rather than a new destructive action. It falls under Write (modifies data reversibly) rather than Destructive, since restoring is the opposite of destruction and the effect is reversible.
From the tool's definition Tool name 'splitwise_restore_expense' and description 'Restore a deleted expense' indicate the tool reverts a deletion by recreating or reactivating expense data.
Attacks that exploit this kind of access
Restore a deleted expense. It is categorised as a Write tool in the Splitwise MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Splitwise MCP Server MCP server in PolicyLayer and add a rule for splitwise_restore_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_restore_expense is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the splitwise_restore_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_restore_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_restore_expense is provided by the Splitwise MCP Server MCP server (svarun115/splitwise-mcp-server). 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 →