WebSocket 연결 상태를 확인합니다.
AI agents call get_connection_status to retrieve information from MCP Mempool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool merely queries the status of a WebSocket connection. It retrieves informational data about connection state with no side effects, no code execution, no data modification, and no destructive operations. It is a straightforward read-only diagnostic query, consistent with other Read category tools like get_mempool_info or get_block_info on the same server.
From the tool's definition Tool name 'get_connection_status' and description 'WebSocket 연결 상태를 확인합니다' (translates to 'Check WebSocket connection status') indicates a status query operation. This retrieves connection state information without modifying or executing any operations.
Attacks that exploit this kind of access
WebSocket 연결 상태를 확인합니다. It is categorised as a Read tool in the MCP Mempool MCP Server, which means it retrieves data without modifying state.
Register the MCP Mempool MCP server in PolicyLayer and add a rule for get_connection_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 MCP Mempool. Nothing to install.
get_connection_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_connection_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_connection_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_connection_status is provided by the MCP Mempool MCP server (jaducku/mcp-mempool). 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 →