Add a comment to an expense.
AI agents use splitwise_add_comment 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.
Adding a comment creates new data in the Splitwise system but does not delete, modify existing records irreversibly, execute code, move money, or trigger external operations. The action is reversible (comments can typically be deleted via splitwise_delete_comment, which exists as a sibling tool), making it a Write operation.
From the tool's definition Tool name 'splitwise_add_comment' and description 'Add a comment to an expense' indicate creation of a new comment record, which is a reversible write operation.
Attacks that exploit this kind of access
Add a comment to an 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_add_comment: 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_comment 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_comment 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_comment. 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_comment 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 →