Look up specific ledger entries by id.
AI agents call query_ledgers to retrieve information from Mcp Kraken without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves ledger data without creating, modifying, deleting, or executing anything. While it accesses financial transaction history on a cryptocurrency exchange, the read-only nature and lack of side effects place it in the Read category with low severity. The main risk is information disclosure of account transaction history, which is limited compared to tools that can execute trades or move funds.
From the tool's definition Tool description states 'Look up specific ledger entries by id' - a query/lookup operation with no modification or execution. The method name 'query_ledgers' further indicates a read-only retrieval action.
Attacks that exploit this kind of access
Look up specific ledger entries by id. It is categorised as a Read tool in the Mcp Kraken MCP Server, which means it retrieves data without modifying state.
Register the Mcp Kraken MCP server in PolicyLayer and add a rule for query_ledgers: 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 Kraken. Nothing to install.
query_ledgers 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 query_ledgers 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 query_ledgers. 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.
query_ledgers is provided by the Mcp Kraken MCP server (xavierbeheydt/mcp-kraken). 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 →