AI agents call get_current_user 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 queries and returns information about the authenticated user (user ID and profile data) without creating, modifying, deleting, or executing any operations. It is a simple read-only informational lookup, consistent with the Read category definition of retrieving data with no side effects.
From the tool's definition Tool name 'get_current_user' and description 'Get the currently authenticated Splitwise user' indicate a data retrieval operation with no side effects.
Attacks that exploit this kind of access
Get the currently authenticated Splitwise user — useful to find your own user ID when creating expense splits. 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_current_user: 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_current_user 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_current_user 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_current_user. 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_current_user 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 →