Create a new sub-account.
AI agents use create_subaccount to create or update resources in Mcp Kraken — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Kraken environment.
This tool creates a new sub-account, which is a reversible write operation that modifies account structure and configuration. It does not delete data (not Destructive), execute arbitrary code (not Execute), or move funds (not Financial). While it has moderate blast radius in a multi-account cryptocurrency context, it is fundamentally a Write operation.
From the tool's definition Tool description states 'Create a new sub-account' - a create operation that modifies account structure. Server context shows this is a Kraken cryptocurrency exchange API with 'account management' capabilities.
Attacks that exploit this kind of access
Create a new sub-account. It is categorised as a Write tool in the Mcp Kraken MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Kraken MCP server in PolicyLayer and add a rule for create_subaccount: 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.
create_subaccount is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_subaccount 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 create_subaccount. 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.
create_subaccount 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 →