Find expense by Amazon order ID in notes field. Most reliable duplicate detection method.
AI agents call splitwise_find_by_order_id 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 or queries existing expense data based on an Amazon order ID without creating, modifying, deleting, or executing any operations. It is purely informational and safe for AI agents to use, making it a Read category risk with low severity.
From the tool's definition Tool name 'find_by_order_id' and description 'Find expense by Amazon order ID in notes field' indicate a search/query operation with no modification of data. The purpose is duplicate detection through lookup.
Attacks that exploit this kind of access
Find expense by Amazon order ID in notes field. Most reliable duplicate detection method. 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_find_by_order_id: 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_find_by_order_id 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_find_by_order_id 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_find_by_order_id. 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_find_by_order_id 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 →