Issue a token for use with the private WebSocket API.
AI agents call get_websockets_token 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 generates a token credential for subsequent WebSocket API authentication. While tokens enable access to private APIs, the token issuance itself is a read-like operation that retrieves credentials without side effects on accounts, balances, or orders. The actual risk materializes only when the token is used by other tools (like add_order or account_transfer).
From the tool's definition Tool description: 'Issue a token for use with the private WebSocket API.' The tool retrieves/generates an authentication token for API access; it does not modify account state, execute trades, move funds, or delete data.
Attacks that exploit this kind of access
Issue a token for use with the private WebSocket API. 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_websockets_token: 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_websockets_token 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_websockets_token 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_websockets_token. 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_websockets_token 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 →