Confirm the pending maintenance margin rate update for a position.\nThis removes the reduce-only restriction that was applied when Bybit adjusted the risk limit.\n\nAgent hint: Use this when a position has isReduceOnly=true due to a risk limit adjustment by Bybit.\nCalling this confirms the new M...
AI agents invoke confirmNewRiskLimit to trigger actions in Bybit MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
While this is not destructive (doesn't delete data) or financial (doesn't move money directly), it is an Execute action because it triggers a real effect on the user's trading position—it lifts restrictions that were previously applied by the exchange.
From the tool's definition Tool 'confirmNewRiskLimit' performs an irreversible state change on a trading position by confirming a maintenance margin rate update and removing trading restrictions ('removes the reduce-only restriction').
Documented attack patterns abuse exactly the kind of access confirmNewRiskLimit 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 confirmNewRiskLimit:
{
"version": "1",
"default": "deny",
"tools": {
"confirmNewRiskLimit": {
"limits": [
{
"counter": "confirmnewrisklimit_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}confirmNewRiskLimit stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Confirm the pending maintenance margin rate update for a position.\nThis removes the reduce-only restriction that was applied when Bybit adjusted the risk limit.\n\nAgent hint: Use this when a position has isReduceOnly=true due to a risk limit adjustment by Bybit.\nCalling this confirms the new MMR and removes the reduce-only restriction.\nCheck isReduceOnly in getPositionInfo to determine if this action is needed. It is categorised as a Execute tool in the Bybit MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for confirmNewRiskLimit: 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.
confirmNewRiskLimit is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the confirmNewRiskLimit 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 confirmNewRiskLimit. 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.
confirmNewRiskLimit 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.