AI agents call asset_info to retrieve information from Kraken Pro MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about assets (e.g., XBT, ETH, USDT) with no side effects. It is purely informational, similar to a data lookup. While it exists on a financial trading server (Kraken Pro), the tool itself only reads and returns static asset information without executing trades, moving funds, or modifying account state.
From the tool's definition Tool name 'asset_info' and description 'Asset metadata' indicate retrieval of read-only information about cryptocurrencies. No mutations, deletions, or financial transactions occur.
Documented attack patterns abuse exactly the kind of access asset_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kraken Pro MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for asset_info:
{
"version": "1",
"default": "deny",
"tools": {
"asset_info": {}
}
}asset_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Asset metadata. Example assets: 'XBT,ETH,USDT'. It is categorised as a Read tool in the Kraken Pro MCP MCP Server, which means it retrieves data without modifying state.
Register the Kraken Pro MCP server in PolicyLayer and add a rule for asset_info: 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 Kraken Pro MCP. Nothing to install.
asset_info 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 asset_info 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 asset_info. 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.
asset_info is provided by the Kraken Pro MCP server (oilst/kraken-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kraken Pro MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 Kraken Pro MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.