Query the Self-Matching Prevention (SMP) group ID associated with the account.\nReturns 0 if the account does not belong to any group.\n\nRate limit: 10 req/s\n\nAgent hint: Use this to check the SMP group assignment. No parameters needed. Returns\nsmpGroup as an integer (0 = no group). SMP group...
AI agents call getSmpGroup to retrieve information from Bybit MCP Server 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 account metadata (SMP group ID) without modifying, deleting, executing operations, or creating financial obligations. It is a read-only information retrieval function with minimal blast radius if misused by an AI agent.
From the tool's definition "Query the Self-Matching Prevention (SMP) group ID associated with the account" — retrieves account group assignment data with no side effects. "Returns smpGroup as an integer" confirms data retrieval. "No parameters needed" indicates a simple lookup.
Documented attack patterns abuse exactly the kind of access getSmpGroup gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bybit MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for getSmpGroup:
{
"version": "1",
"default": "deny",
"tools": {
"getSmpGroup": {}
}
} getSmpGroup is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Query the Self-Matching Prevention (SMP) group ID associated with the account.\nReturns 0 if the account does not belong to any group.\n\nRate limit: 10 req/s\n\nAgent hint: Use this to check the SMP group assignment. No parameters needed. Returns\nsmpGroup as an integer (0 = no group). SMP groups prevent self-matching\nbetween accounts in the same group. It is categorised as a Read tool in the Bybit MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for getSmpGroup: 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.
getSmpGroup 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 getSmpGroup 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 getSmpGroup. 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.
getSmpGroup 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.
Start from Bybit MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
326 Bybit MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.