AI agents call get_groups to retrieve information from Splitwise without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing group data and their associated information. It has no side effects, does not modify any data, and does not execute code or trigger external operations. It is purely informational, making it a Read category tool with low severity since unauthorized access would only expose group structure and debt information without enabling financial transactions or destructive actions.
From the tool's definition Tool name 'get_groups' and description 'List all Splitwise groups' indicate a read-only retrieval operation. The description specifies it provides group information and member details without any modification, creation, or deletion of data.
Attacks that exploit this kind of access
List all Splitwise groups with member details, group IDs, and current debts within each group. It is categorised as a Read tool in the Splitwise MCP Server, which means it retrieves data without modifying state.
Register the Splitwise MCP server in PolicyLayer and add a rule for get_groups: 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. Nothing to install.
get_groups is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_groups 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 get_groups. 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.
get_groups is provided by the Splitwise MCP server (saharshpatel24/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 →