Query Market Maker Protection configuration and freeze status for the specified\nbase coin. Returns MMP parameters and current state.\n\nRate limit: 5 req/s\n\nAgent hint: Use this to check MMP settings and freeze status. The baseCoin parameter is required.\nKey fields: mmpEnabled (whether MMP is...
AI agents call getMmpState 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 retrieves and queries the current state of Market Maker Protection settings for a given base coin. It has no side effects, does not modify data, execute code, or commit financial transactions. It is a straightforward informational read operation with minimal risk if misused by an AI agent.
From the tool's definition Tool name 'getMmpState' and description 'Query Market Maker Protection configuration and freeze status' — purely queries and returns configuration data without modifying or executing actions.
Documented attack patterns abuse exactly the kind of access getMmpState 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 getMmpState:
{
"version": "1",
"default": "deny",
"tools": {
"getMmpState": {}
}
}getMmpState 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.
Query Market Maker Protection configuration and freeze status for the specified\nbase coin. Returns MMP parameters and current state.\n\nRate limit: 5 req/s\n\nAgent hint: Use this to check MMP settings and freeze status. The baseCoin parameter is required.\nKey fields: mmpEnabled (whether MMP is active), window (time window in ms),\nfrozenPeriod (freeze duration in ms), qtyLimit, deltaLimit, mmpFrozen (current\nfreeze status), mmpFrozenUntil (freeze expiry timestamp). 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 getMmpState: 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.
getMmpState 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 getMmpState 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 getMmpState. 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.
getMmpState 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.