This record as markdown: /tools/johnnywic-bybit-mcp/set-mmp.md
What set_mmp does on Bybit
AI agents use set_mmp to create or update resources in Bybit, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bybit environment.
Why set_mmp is rated Medium
Setting MMP parameters is a configuration change that adjusts trading protection thresholds and behaviors. This is reversible (parameters can be adjusted again) and does not irreversibly delete data or execute arbitrary code. While it affects trading operations, it is not immediately financial (no money moves) and not destructive.
From the tool's definition Tool name 'set_mmp' and description 'Set Market Maker Protection (MMP) parameters' indicate configuration modification of trading protection settings. The verb 'set' in both name and description confirms this creates or modifies data reversibly.
Attacks that exploit this kind of access
The rule that runs set_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 set_mmp, this is the rule to start with:
set_mmp stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 set_mmp call is checked against it from then on.
Questions about set_mmp
Set Market Maker Protection (MMP) parameters. It is categorised as a Write tool in the Bybit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bybit MCP server in PolicyLayer and add a rule for set_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.
set_mmp is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_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 set_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.
set_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.
This server
Across the catalogue