Creates an Iceberg strategy that splits a large order into multiple smaller child orders,\ndisplaying only one at a time to hide trading intent.\n\nWhen to use:\n- You have a large order and want to hide total size from the market\n- You want to prevent price manipulation based on your order size...
AI agents use createIcebergStrategy to commit financial operations through Bybit MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly places trading orders on a live cryptocurrency exchange, committing financial obligations and executing trades. It is a financial action with critical blast radius since an AI agent could execute large-volume trades that move markets or cause significant financial loss.
From the tool's definition Creates an Iceberg strategy that splits a large order into multiple smaller child orders — involves placing real trading orders on the Bybit cryptocurrency exchange
Documented attack patterns abuse exactly the kind of access createIcebergStrategy gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bybit MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for createIcebergStrategy:
{
"version": "1",
"default": "deny",
"tools": {
"createIcebergStrategy": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}Any call to createIcebergStrategy is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Creates an Iceberg strategy that splits a large order into multiple smaller child orders,\ndisplaying only one at a time to hide trading intent.\n\nWhen to use:\n- You have a large order and want to hide total size from the market\n- You want to prevent price manipulation based on your order size\n- You need to reduce market impact while maintaining consistent pricing\n- You want to earn maker rebates by using post-only orders\n\nExecution behavior:\n1. Calculate child order size:\n - If subSize provided: orderCount = size / subSize\n - If orderCount provided: subSize = size / orderCount\n2. Create first child order (limit or chase pricing)\n3. Wait for child order to fill completely\n4. Once filled, create next child order\n5. Repeat until all size is executed\n6. Each child order is independent - can have different prices if chasing\n\nImportant notes:\n- Recommended subSize: 5%-20% of total size\n- Enable postOnly=1 to get maker fee rebates\n- Set chaseDistance=\. It is categorised as a Financial tool in the Bybit MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for createIcebergStrategy: 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 MCP Server. Nothing to install.
createIcebergStrategy 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 createIcebergStrategy 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 createIcebergStrategy. 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.
createIcebergStrategy is provided by the Bybit MCP Server MCP server (bybit-exchange/trading-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bybit MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
326 Bybit MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.