AI agents call get_api_usage 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 current API usage statistics against the rate limit. It performs no data modification, financial transactions, or destructive operations. The '[0 API calls]' notation indicates it is a metadata/monitoring query. While the server manages financial data (budgets, accounts, transactions), this specific tool is a read-only query with minimal blast radius if misused by an agent.
From the tool's definition Tool name is 'get_api_usage' and description states it 'Check[s] current YNAB API usage' — a pure query operation that retrieves usage metrics without modifying any state.
Attacks that exploit this kind of access
[0 API calls] Check current YNAB API usage against the 200 calls/hour rate limit. 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_api_usage: 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_api_usage 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_api_usage 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_api_usage. 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_api_usage 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.
get_api_usage is one line of Ynab's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →