websocket_connect

A execute tool on the Allcanuse MCP server.

SERVERAllcanuse SOURCEra1nyxin/allcanuse-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ra1nyxin-allcanuse-mcp/websocket-connect.md

WHAT IT DOES

What websocket_connect does on Allcanuse

AI agents invoke websocket_connect to trigger actions in Allcanuse. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why websocket_connect is rated High

The name implies establishing a WebSocket connection to an external endpoint, which is an external network operation. Given the server context (90+ tools for system management including command execution and network diagnostics), this likely initiates a persistent network connection. Empty description lowers confidence.

From the tool's definition Tool name 'websocket_connect' on a server that provides 'command execution' and 'external operations'. Description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs websocket_connect safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Allcanuse, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For websocket_connect, this is the rule to start with:

websocket_connect Rate-limited

websocket_connect stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "websocket_connect": {
      "limits": [
        {
          "counter": "websocket_connect_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Allcanuse, apply this rule, and every websocket_connect call is checked against it from then on.

FAQ

Questions about websocket_connect

What does the websocket_connect tool do? +

websocket_connect is a execute tool on the Allcanuse MCP server. It is categorised as a Execute tool in the Allcanuse MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on websocket_connect? +

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

What risk level is websocket_connect? +

websocket_connect is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit websocket_connect? +

Yes. Add a rate_limit block to the websocket_connect 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 websocket_connect completely? +

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

websocket_connect is provided by the Allcanuse MCP server (ra1nyxin/allcanuse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Allcanuse, and thousands of servers like it.

This server

All 130 Allcanuse tools → High-risk tools on this server →

Across the catalogue

adb_connect_device on Android Forensics ADB MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →