example_queries
AI agents call example_queries to retrieve information from MCP Beancount Tool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Without a description, classification relies on the tool name. 'Example_queries' most naturally implies retrieving or listing example query templates rather than executing queries, modifying data, or performing destructive operations. The tool name suggests informational/retrieval use (Read category).
From the tool's definition Tool name 'example_queries' suggests retrieval of example queries; no description provided to confirm function. Based on naming convention and server context (Beancount accounting ledger), likely provides read-only access to predefined query examples.
Attacks that exploit this kind of access
example_queries. It is categorised as a Read tool in the MCP Beancount Tool MCP Server, which means it retrieves data without modifying state.
Register the MCP Beancount Tool MCP server in PolicyLayer and add a rule for example_queries: 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 MCP Beancount Tool. Nothing to install.
example_queries 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 example_queries 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 example_queries. 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.
example_queries is provided by the MCP Beancount Tool MCP server (onesvat/mcp-beancount). 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 →