Sync local cache with Splitwise API. Fetches recent expenses and updates cache.
AI agents call splitwise_sync_cache to retrieve information from Splitwise MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data from the Splitwise API and updates a local cache—a read operation with no side effects on the source system. It has no ability to modify, delete, or execute external operations. The blast radius is minimal: a sync failure affects only the local cache state, not user data or financial records.
From the tool's definition The tool 'splitwise_sync_cache' performs a fetch operation that 'Fetches recent expenses and updates cache' with no destructive, write, or execution capabilities described.
Attacks that exploit this kind of access
Sync local cache with Splitwise API. Fetches recent expenses and updates cache. It is categorised as a Read tool in the Splitwise MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Splitwise MCP Server MCP server in PolicyLayer and add a rule for splitwise_sync_cache: 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_sync_cache 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 splitwise_sync_cache 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_sync_cache. 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_sync_cache is provided by the Splitwise MCP Server MCP server (vishnujayvel/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 →