Get information about a counterparty user in a specific order.\n\nAgent hint: Only query the counterparty of the current active order. Do NOT enumerate arbitrary UIDs or call this in a loop — it exposes PII of unrelated users.
AI agents call getCounterpartyUserInfo 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 is fundamentally a Read operation—it retrieves user information without modifying data. However, severity is elevated to 'medium' rather than 'low' because the tool accesses PII (personally identifiable information) of counterparty users.
From the tool's definition Tool name 'getCounterpartyUserInfo' and description 'Get information about a counterparty user' indicates data retrieval. The agent hint explicitly warns 'it exposes PII of unrelated users,' acknowledging personally identifiable information exposure risk.
Documented attack patterns abuse exactly the kind of access getCounterpartyUserInfo 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 getCounterpartyUserInfo:
{
"version": "1",
"default": "deny",
"tools": {
"getCounterpartyUserInfo": {}
}
}getCounterpartyUserInfo 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.
Get information about a counterparty user in a specific order.\n\nAgent hint: Only query the counterparty of the current active order. Do NOT enumerate arbitrary UIDs or call this in a loop — it exposes PII of unrelated users. 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 getCounterpartyUserInfo: 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.
getCounterpartyUserInfo 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 getCounterpartyUserInfo 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 getCounterpartyUserInfo. 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.
getCounterpartyUserInfo 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.