This record as markdown: /tools/johnnywic-bybit-mcp/reset-mmp.md
What reset_mmp does on Bybit
AI agents invoke reset_mmp to trigger actions in Bybit. 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.
Why reset_mmp is rated High
Resetting MMP re-enables automated market-making order flow on the exchange. It is not simply a data read or write; it triggers an operational state change on the exchange (unblocking order submission). Misuse could expose the account to unintended mass order placement in volatile markets, making it high severity.
From the tool's definition Reset Market Maker Protection (MMP) — triggers an external operation on the exchange that re-enables market-making activity after a protection halt
Attacks that exploit this kind of access
The rule that runs reset_mmp safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reset_mmp, this is the rule to start with:
reset_mmp 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Bybit, apply this rule, and every reset_mmp call is checked against it from then on.
Questions about reset_mmp
Reset Market Maker Protection (MMP). It is categorised as a Execute tool in the Bybit MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Bybit MCP server in PolicyLayer and add a rule for reset_mmp: 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. Nothing to install.
reset_mmp 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 reset_mmp 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 reset_mmp. 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.
reset_mmp is provided by the Bybit MCP server (johnnywic/bybit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Bybit, and thousands of servers like it.
Across the catalogue