Return recent bid/ask spread snapshots.
AI agents call get_recent_spreads 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 historical market spread data from the Kraken exchange without any side effects. It does not execute trades, transfer funds, modify orders, or alter any state. The blast radius of misuse is minimal—an agent could only retrieve public market information already available through normal API queries. This is a straightforward Read operation.
From the tool's definition get_recent_spreads returns bid/ask spread snapshots with no modification, creation, or deletion of data. The verb 'get' and the read-only nature of market data retrieval indicates a data query operation.
Attacks that exploit this kind of access
Return recent bid/ask spread snapshots. 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 get_recent_spreads: 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.
get_recent_spreads 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_recent_spreads 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_recent_spreads. 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_recent_spreads 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 →