Get detailed information about a specific history entry including before/after state.
AI agents call get_history_entry 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.
This tool retrieves audit or change history information from YNAB without creating, modifying, deleting, or executing operations. It has no side effects and presents minimal risk—it only exposes historical metadata that reflects past changes. Misuse would be limited to unauthorized information disclosure rather than operational damage.
From the tool's definition Tool name 'get_history_entry' and description 'Get detailed information about a specific history entry' clearly indicate retrieval of historical data without modification.
Attacks that exploit this kind of access
Get detailed information about a specific history entry including before/after state. 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 get_history_entry: 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.
get_history_entry 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_history_entry 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_history_entry. 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_history_entry 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 →