create_internal_transfer
A financial tool on the Bybit MCP server.
This record as markdown: /tools/johnnywic-bybit-mcp/create-internal-transfer.md
What create_internal_transfer does on Bybit
AI agents use create_internal_transfer to commit financial operations through Bybit, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why create_internal_transfer is rated Critical
Although the description is empty (lowering confidence slightly from 1.0), the tool name combined with the server context (Bybit exchange with 246 trading/account management tools) makes it clear this tool moves money or financial assets. This is Financial category per definition ('moves money or commits financial obligations').
From the tool's definition Tool name 'create_internal_transfer' on a Bybit exchange MCP server indicates movement of funds between internal accounts. Bybit is a cryptocurrency trading platform where internal transfers represent movement of financial assets.
Attacks that exploit this kind of access
The rule that runs create_internal_transfer 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_internal_transfer, this is the rule to start with:
Any call to create_internal_transfer is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Bybit, apply this rule, and every create_internal_transfer call is checked against it from then on.
Questions about create_internal_transfer
create_internal_transfer is a financial tool on the Bybit MCP server. It is categorised as a Financial tool in the Bybit MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Bybit MCP server in PolicyLayer and add a rule for create_internal_transfer: 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_internal_transfer is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the create_internal_transfer 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_internal_transfer. 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_internal_transfer 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.
Across the catalogue