This record as markdown: /tools/johnnywic-bybit-mcp/get-smp-group.md
What get_smp_group does on Bybit
AI agents call get_smp_group to retrieve information from Bybit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_smp_group is rated Low
This tool retrieves a Self Match Prevention group ID, which is a read-only query of existing account or exchange configuration data. It has no side effects, does not execute orders, and does not move funds or modify any state. The 'get' prefix and 'Get' verb in the description confirm it is a retrieval operation, placing it firmly in the Read category with low severity.
From the tool's definition Tool name 'get_smp_group' and description 'Get Self Match Prevention (SMP) group ID' indicate a retrieval operation that queries configuration or account settings without modifying or executing trades.
Attacks that exploit this kind of access
The rule that runs get_smp_group safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_smp_group, this is the rule to start with:
get_smp_group is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Bybit, apply this rule, and every get_smp_group call is checked against it from then on.
Questions about get_smp_group
Get Self Match Prevention (SMP) group ID. 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_smp_group: 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_smp_group 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_smp_group 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_smp_group. 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_smp_group 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.
More on Bybit, and thousands of servers like it.
This server
Across the catalogue