New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

tcp_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/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.

Questions about tcp_connect

What does the tcp_connect tool do? +

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.

How do I enforce a policy on tcp_connect? +

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.

What risk level is tcp_connect? +

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

Can I rate-limit tcp_connect? +

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.

How do I block tcp_connect completely? +

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.

What MCP server provides tcp_connect? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Allcanuse's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.