Add a new friend. If the user exists, first_name and last_name are ignored. If creating a new user, first_name is required.
AI agents use splitwise_add_friend 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 creates or modifies the user's social graph by adding friends, which is a reversible Write operation. While not destructive, it modifies application state and can affect expense-sharing permissions and financial workflows.
From the tool's definition Tool creates a new friend relationship or adds an existing user to a friend list. The description states 'Add a new friend' and 'If creating a new user', indicating data creation.
Attacks that exploit this kind of access
Add a new friend. If the user exists, first_name and last_name are ignored. If creating a new user, first_name is required. 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_add_friend: 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_add_friend 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_add_friend 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_add_friend. 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_add_friend 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 →