Set trading stop
AI agents use set_trading_stop to commit financial operations through Bybit MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Setting a trading stop directly modifies active trade parameters on a live financial exchange, potentially triggering automatic order execution (closing positions) that results in real financial transactions. This falls squarely in the Financial category as it commits or alters financial obligations on a cryptocurrency exchange. Misuse could cause unintended position closures or significant financial loss.
From the tool's definition 'Set trading stop' on a server that enables 'cryptocurrency trading on Bybit exchange' with 'automated trading operations' and 'trailing stop losses'
Attacks that exploit this kind of access
Set trading stop. It is categorised as a Financial tool in the Bybit MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for set_trading_stop: 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.
set_trading_stop is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the set_trading_stop 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_trading_stop. 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_trading_stop is provided by the Bybit MCP Server MCP server (kondisettyravi/mcp-bybit-node). 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 →