AI agents call get_scheduled_transaction 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 retrieves information about an existing scheduled transaction without modifying, creating, or deleting any data. It is a read-only query operation with no side effects. While the server overall deals with financial data, this specific tool performs only information retrieval, making it low severity.
From the tool's definition Tool name contains 'get' and description states 'Get details for a single scheduled transaction' with no modification, creation, or deletion capabilities
Attacks that exploit this kind of access
[1 API call] Get details for a single scheduled transaction. 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_scheduled_transaction: 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_scheduled_transaction 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_scheduled_transaction 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_scheduled_transaction. 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_scheduled_transaction 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 →