AI agents call get_trade_behaviour_config to retrieve information from Bybit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries trade behaviour configuration data without side effects. It falls squarely into the Read category. On a financial exchange server, reading configuration poses minimal risk compared to execution or financial transaction tools also present on this server. Severity is low because configuration data disclosure alone does not enable unauthorized transactions or irreversible changes.
From the tool's definition Tool name and description indicate retrieval of configuration settings: 'Get trade behaviour configuration settings.' No creation, modification, deletion, code execution, or financial operations are described.
Attacks that exploit this kind of access
Get trade behaviour configuration settings. It is categorised as a Read tool in the Bybit MCP Server, which means it retrieves data without modifying state.
Register the Bybit MCP server in PolicyLayer and add a rule for get_trade_behaviour_config: 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.
get_trade_behaviour_config 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_trade_behaviour_config 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_trade_behaviour_config. 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_trade_behaviour_config 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.
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 →