tcp_connect
A execute tool on the Allcanuse MCP server.
This record as markdown: /tools/ra1nyxin-allcanuse-mcp/tcp-connect.md
What tcp_connect does on Allcanuse
AI agents invoke tcp_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.
Why tcp_connect is rated High
A TCP connect tool initiates outbound network connections to arbitrary hosts and ports, which can be used for data exfiltration, port scanning, or connecting to malicious services. The server context mentions 'network diagnostics' among its capabilities. With an empty description, confidence is reduced, but the name strongly implies Execute-level network operation with high potential blast radius.
From the tool's definition Tool name 'tcp_connect' suggests initiating a TCP network connection; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs tcp_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 tcp_connect, this is the rule to start with:
tcp_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Allcanuse, apply this rule, and every tcp_connect call is checked against it from then on.
Questions about tcp_connect
tcp_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.
Register the Allcanuse MCP server in PolicyLayer and add a rule for tcp_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.
tcp_connect is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the tcp_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.
Set action: deny in the PolicyLayer policy for tcp_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.
tcp_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.
More on Allcanuse, and thousands of servers like it.
Across the catalogue