AI agents call get_payee_locations_for_payee to retrieve information from Ynab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads/retrieves GPS location data associated with a payee. It performs a query operation (1 API call to fetch data) with no side effects, data modifications, or financial operations. The blast radius of misuse is minimal - exposure would be limited to location history visibility. Even in the context of a financial management server (YNAB), this particular tool is purely informational retrieval.
From the tool's definition Tool description explicitly states 'Get all GPS locations for a specific payee' - a retrieval operation with no modification, deletion, or financial transaction capability.
Attacks that exploit this kind of access
[1 API call] Get all GPS locations for a specific payee. It is categorised as a Read tool in the Ynab MCP Server, which means it retrieves data without modifying state.
Register the Ynab MCP server in PolicyLayer and add a rule for get_payee_locations_for_payee: 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 Ynab. Nothing to install.
get_payee_locations_for_payee 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_payee_locations_for_payee 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_payee_locations_for_payee. 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_payee_locations_for_payee is provided by the Ynab MCP server (justmytwospence/ynab-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 →