Low Risk

get_websocket_messages

Lists WebSocket connections or gets messages for a specific connection. Without wsid, lists all connections. With wsid, gets messages.

How to control get_websocket_messages ↓

AI agents call get_websocket_messages to retrieve information from MiniApp CDP MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool only retrieves and queries existing WebSocket connection data and message history. It performs no side effects, does not execute code, and does not modify state.

From the tool's definition Tool description states it 'Lists WebSocket connections or gets messages for a specific connection' - purely retrieval operations with no modification or execution capability. The verb 'gets' and 'lists' indicate read-only semantics.

Documented attack patterns abuse exactly the kind of access get_websocket_messages gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and MiniApp CDP MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_websocket_messages:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_websocket_messages": {}
  }
}

get_websocket_messages is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MiniApp CDP MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_websocket_messages tool do? +

Lists WebSocket connections or gets messages for a specific connection. Without wsid, lists all connections. With wsid, gets messages. It is categorised as a Read tool in the MiniApp CDP MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_websocket_messages? +

Register the MiniApp CDP MCP server in PolicyLayer and add a rule for get_websocket_messages: 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 MiniApp CDP MCP. Nothing to install.

What risk level is get_websocket_messages? +

get_websocket_messages is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_websocket_messages? +

Yes. Add a rate_limit block to the get_websocket_messages 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.

How do I block get_websocket_messages completely? +

Set action: deny in the PolicyLayer policy for get_websocket_messages. 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.

What MCP server provides get_websocket_messages? +

get_websocket_messages is provided by the MiniApp CDP MCP server (zhizhuodemao/miniapp-cdp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MiniApp CDP MCP tool call.

Deterministic rules across all 18 MiniApp CDP MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

18 MiniApp CDP MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.