New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

setHedgingMode

Enable or disable PM include spot hedging mode

SERVERBybit MCP Server SOURCEbybit-exchange/trading-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/bybit-exchange-trading-mcp/sethedgingmode.md

What setHedgingMode does on Bybit MCP Server

AI agents use setHedgingMode to create or update resources in Bybit MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bybit MCP Server environment.

Why setHedgingMode is rated Medium

This tool changes account-level trading mode settings, which is a configuration modification. It is reversible (can be toggled back), so it does not qualify as Destructive. It does not execute arbitrary code or transactions, so it is not Execute. It does not directly move funds, so it is not Financial. It is Write because it modifies account state.

From the tool's definition Tool description indicates it 'Enable or disable PM include spot hedging mode' — this modifies account configuration settings on the Bybit exchange. The action is reversible (can toggle hedging mode on and off).

Questions about setHedgingMode

What does the setHedgingMode tool do? +

Enable or disable PM include spot hedging mode. It is categorised as a Write tool in the Bybit MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on setHedgingMode? +

Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for setHedgingMode: 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.

What risk level is setHedgingMode? +

setHedgingMode is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit setHedgingMode? +

Yes. Add a rate_limit block to the setHedgingMode 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.

How do I block setHedgingMode completely? +

Set action: deny in the PolicyLayer policy for setHedgingMode. 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.

What MCP server provides setHedgingMode? +

setHedgingMode 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.

More on Bybit MCP Server, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Bybit MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.