List recent write operations with their IDs for undo. Operations are listed in reverse chronological order (newest first).
AI agents call list_history to retrieve information from YNAB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite being hosted on a financial management server (YNAB), this tool only reads/retrieves a log of past operations. It does not create, modify, delete, or execute any financial transactions—it merely displays historical metadata about write operations that were already performed.
From the tool's definition Tool description states it 'List[s] recent write operations' and is designed for 'undo' purposes. The verb 'list' and the read-only nature of retrieving operation history (not executing or modifying anything) make this a retrieval operation.
Attacks that exploit this kind of access
List recent write operations with their IDs for undo. Operations are listed in reverse chronological order (newest first). It is categorised as a Read tool in the YNAB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the YNAB MCP Server MCP server in PolicyLayer and add a rule for list_history: 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 MCP Server. Nothing to install.
list_history 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 list_history 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 list_history. 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.
list_history is provided by the YNAB MCP Server MCP server (jeangnc/ynab-mcp-server). 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 →