This record as markdown: /tools/johnnywic-bybit-mcp/create-sub-api-key.md
What create_sub_api_key does on Bybit
AI agents use create_sub_api_key to create or update resources in Bybit, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bybit environment.
Why create_sub_api_key is rated Medium
This tool creates new API credentials for a sub-account, which modifies the account's security posture and access control structure. While reversible (keys can be deleted), creating API keys grants new access and can expose trading and account management capabilities to third parties.
From the tool's definition Tool name: 'create_sub_api_key'. Description: 'Create API key for a sub UID.' The word 'Create' indicates this tool generates new credentials/configurations.
Attacks that exploit this kind of access
The rule that runs create_sub_api_key safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_sub_api_key, this is the rule to start with:
create_sub_api_key stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Bybit, apply this rule, and every create_sub_api_key call is checked against it from then on.
Questions about create_sub_api_key
Create API key for a sub UID. It is categorised as a Write tool in the Bybit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bybit MCP server in PolicyLayer and add a rule for create_sub_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 Bybit. Nothing to install.
create_sub_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 create_sub_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 create_sub_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.
create_sub_api_key is provided by the Bybit MCP server (johnnywic/bybit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Bybit, and thousands of servers like it.
This server
Across the catalogue