Get current leverage and margin mode settings for a symbol.
AI agents call get_leverage_margin_mode to retrieve information from Bitunix MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns existing leverage and margin mode settings for a trading symbol. It has no side effects—it does not create, modify, delete, or execute any trades or financial transactions. The 'get' verb and retrieval-focused description confirm it is a Read operation. While the Bitunix server overall enables Financial operations, this specific tool is purely informational.
From the tool's definition Tool name 'get_leverage_margin_mode' and description 'Get current leverage and margin mode settings for a symbol' indicate a read-only query operation that retrieves configuration state without modifying or executing trades.
Attacks that exploit this kind of access
Get current leverage and margin mode settings for a symbol. It is categorised as a Read tool in the Bitunix MCP MCP Server, which means it retrieves data without modifying state.
Register the Bitunix MCP server in PolicyLayer and add a rule for get_leverage_margin_mode: 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 Bitunix MCP. Nothing to install.
get_leverage_margin_mode 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 get_leverage_margin_mode 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 get_leverage_margin_mode. 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.
get_leverage_margin_mode is provided by the Bitunix MCP server (luiinventions/bitunix-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →