getFMartLimit
Validates the input parameters for creating a futures Martingale bot and\nreturns the allowable ranges for each parameter (price float percentage,\nadd position ratio, add position count, initial margin, round TP percentage,\nstop-loss, entry price, leverage).\n\nUse this endpoint before calling ...
This record as markdown: /tools/bybit-exchange-trading-mcp/getfmartlimit.md
What getFMartLimit does on Bybit MCP Server
AI agents call getFMartLimit to retrieve information from Bybit MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getFMartLimit is rated Low
This tool performs input validation and returns metadata about acceptable parameter ranges. It has no side effects on accounts, positions, or financial state. While it relates to trading bot creation, the tool itself only queries and returns constraint information, making it a Read operation.
From the tool's definition The tool 'Validates the input parameters' and 'returns the allowable ranges for each parameter' — it retrieves validation constraints without creating, modifying, deleting, or executing trades.
Attacks that exploit this kind of access
The rule that runs getFMartLimit safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getFMartLimit, this is the rule to start with:
getFMartLimit is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Bybit MCP Server, apply this rule, and every getFMartLimit call is checked against it from then on.
Questions about getFMartLimit
Validates the input parameters for creating a futures Martingale bot and\nreturns the allowable ranges for each parameter (price float percentage,\nadd position ratio, add position count, initial margin, round TP percentage,\nstop-loss, entry price, leverage).\n\nUse this endpoint before calling /v5/fmartingalebot/create\nto ensure parameters are within valid bounds. The response includes a check_code\nthat indicates which parameter is out of range if validation fails.\n\nRate limit: 100 requests per second per IP.\n\nAgent hint: Call this endpoint first to get valid parameter ranges before creating a\nMartingale bot. If check_code is non-zero, the specific validation error\nis indicated by the code value. The response ranges tell you the exact\nmin/max values allowed for each parameter. 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 getFMartLimit: 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.
getFMartLimit 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 getFMartLimit 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 getFMartLimit. 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.
getFMartLimit 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.
More on Bybit MCP Server, and thousands of servers like it.
This server
Across the catalogue