Track the progress of a pending allocation.
AI agents call get_earn_allocation_status 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 status information about an ongoing earn allocation. The verb 'track' and 'get' are indicative of read-only operations that query data without modifying, creating, deleting, or executing transactions. While it operates in the financial domain (cryptocurrency), it does not move money or create financial obligations—it merely reports the state of a previously initiated allocation.
From the tool's definition Tool name 'get_earn_allocation_status' and description 'Track the progress of a pending allocation' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
Track the progress of a pending allocation. 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_earn_allocation_status: 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_earn_allocation_status 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_earn_allocation_status 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_earn_allocation_status. 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_earn_allocation_status 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 →