Retrieves comprehensive details for a specific futures Martingale bot, including\nconfiguration (symbol, mode, leverage, price trigger, add position settings),\ncurrent display status, PnL metrics (realized, unrealized, total), position info\n(size, average price, balances), round progress (compl...
AI agents call getFMartDetail 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 tool queries and returns information about an existing Martingale bot's state without modifying, executing, or deleting anything. It is a pure read operation that gathers data about bot configuration and performance metrics.
From the tool's definition Retrieves comprehensive details for a specific futures Martingale bot, including configuration, current display status, PnL metrics, position info, and timestamps.
Documented attack patterns abuse exactly the kind of access getFMartDetail 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 getFMartDetail:
{
"version": "1",
"default": "deny",
"tools": {
"getFMartDetail": {}
}
}getFMartDetail 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.
Retrieves comprehensive details for a specific futures Martingale bot, including\nconfiguration (symbol, mode, leverage, price trigger, add position settings),\ncurrent display status, PnL metrics (realized, unrealized, total), position info\n(size, average price, balances), round progress (completed rounds, current round,\ncurrent adds), margin balances, and timestamps.\n\nThe bot_id is a numeric ID obtained from createFMartBot or bot listing endpoints.\n\nRate limit: 10 requests per second per UID.\n\nAgent hint: Use this endpoint to check the status and performance of a Martingale bot.\nThe response contains all PnL fields, position details, round progress\n(completed_rounds, current_round, current_added_pos_num), and close reason\nif the bot has stopped. Prefer this over other endpoints when answering\nquestions about a specific bot. 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 getFMartDetail: 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.
getFMartDetail 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 getFMartDetail 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 getFMartDetail. 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.
getFMartDetail 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.