Get status of all real-time WebSocket subscriptions.
AI agents call get_realtime_status to retrieve information from Polymarket 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 the status of existing WebSocket subscriptions, returning metadata about active connections. It is purely informational (Read category), poses minimal security risk (low severity) even in a financial context since it only retrieves state without executing trades or moving funds, and the clarity of intent supports high confidence.
From the tool's definition Tool name 'get_realtime_status' and description 'Get status of all real-time WebSocket subscriptions' indicate retrieval of subscription state information with no modification or execution of external operations.
Attacks that exploit this kind of access
Get status of all real-time WebSocket subscriptions. It is categorised as a Read tool in the Polymarket MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Polymarket MCP Server MCP server in PolicyLayer and add a rule for get_realtime_status: 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 Polymarket MCP Server. Nothing to install.
get_realtime_status 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_realtime_status 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_realtime_status. 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_realtime_status is provided by the Polymarket MCP Server MCP server (nancheng582-jpg/polymarket-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 →