Create new API key for automated trading
AI agents use charisma_create_api_key to create or update resources in Stacks AI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stacks AI MCP Server environment.
This tool creates (Write) new API keys, which are reversible credentials that can be deleted or regenerated. However, the severity is high because a misused API key could enable unauthorized access to trading operations and financial transactions. While the tool itself only creates the key (not executing trades), it removes a barrier to future financial misuse.
From the tool's definition Tool name 'charisma_create_api_key' and description 'Create new API key for automated trading' indicate creation of authentication credentials that enable future automated trading operations.
Attacks that exploit this kind of access
Create new API key for automated trading. It is categorised as a Write tool in the Stacks AI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Stacks AI MCP Server MCP server in PolicyLayer and add a rule for charisma_create_api_key: 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 Stacks AI MCP Server. Nothing to install.
charisma_create_api_key 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 charisma_create_api_key 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 charisma_create_api_key. 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.
charisma_create_api_key is provided by the Stacks AI MCP Server MCP server (stack-ai-mcp/stacks-mcp-server). 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 →