modify_sub_api_key

Modify sub API key permissions.

SERVERBybit SOURCEjohnnywic/bybit-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/johnnywic-bybit-mcp/modify-sub-api-key.md

WHAT IT DOES

What modify_sub_api_key does on Bybit

AI agents use modify_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.

RISK

Why modify_sub_api_key is rated Medium

This tool modifies (Write category) API key permissions, which affects authentication and authorization scope. While reversible, misuse could grant an attacker elevated permissions to control trading, account access, or data retrieval across the exchange platform.

From the tool's definition Tool name 'modify_sub_api_key' and description 'Modify sub API key permissions' indicate reversible modification of API key access controls.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs modify_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 modify_sub_api_key, this is the rule to start with:

modify_sub_api_key Rate-limited

modify_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "modify_sub_api_key": {
      "limits": [
        {
          "counter": "modify_sub_api_key_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Bybit, apply this rule, and every modify_sub_api_key call is checked against it from then on.

FAQ

Questions about modify_sub_api_key

What does the modify_sub_api_key tool do? +

Modify sub API key permissions. 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.

How do I enforce a policy on modify_sub_api_key? +

Register the Bybit MCP server in PolicyLayer and add a rule for modify_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.

What risk level is modify_sub_api_key? +

modify_sub_api_key is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit modify_sub_api_key? +

Yes. Add a rate_limit block to the modify_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.

How do I block modify_sub_api_key completely? +

Set action: deny in the PolicyLayer policy for modify_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.

What MCP server provides modify_sub_api_key? +

modify_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.

KEEP EXPLORING

More on Bybit, and thousands of servers like it.

This server

All 245 Bybit tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →