Validate an order before placing it to check margin requirements.\n\n- Futures and options only (linear, option categories)\n- Returns pre/post margin rates (IMR and MMR) in E4 format\n- Request parameters are the same as Create Order\n- Useful for checking if an order would be rejected due to in...
AI agents call preCheckOrder to retrieve information from Bybit MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a query/validation tool that retrieves pre-trade margin calculations without side effects. It reads account and order data to compute hypothetical margin requirements but does not execute, write, or commit any financial transaction. The tool is designed specifically as a pre-flight check, making it a Read operation.
From the tool's definition Tool description explicitly states 'Validate an order before placing it' and 'Does not actually place the order'. It returns margin rates (IMR and MMR) without creating, modifying, or executing any real trade.
Documented attack patterns abuse exactly the kind of access preCheckOrder 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 preCheckOrder:
{
"version": "1",
"default": "deny",
"tools": {
"preCheckOrder": {}
}
}preCheckOrder is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Validate an order before placing it to check margin requirements.\n\n- Futures and options only (linear, option categories)\n- Returns pre/post margin rates (IMR and MMR) in E4 format\n- Request parameters are the same as Create Order\n- Useful for checking if an order would be rejected due to insufficient margin\n- Does not actually place the order\n\nAgent hint: Use this endpoint to validate margin requirements before placing an order. Does not actually create an order. Only works for futures and options.\nTradFi: use to pre-validate margin for equity perpetuals and commodity perpetuals (category=linear) before placing. It is categorised as a Read tool in the Bybit MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for preCheckOrder: 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.
preCheckOrder is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the preCheckOrder 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 preCheckOrder. 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.
preCheckOrder 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.