scan_ports

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/scan-ports.md

WHAT IT DOES

What scan_ports does on Allcanuse

AI agents invoke scan_ports 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 scan_ports is rated High

Port scanning involves actively probing network hosts/ports, which constitutes an external operation with side effects beyond simple data retrieval. On a server explicitly providing 'network diagnostics' tools, scan_ports likely performs active network reconnaissance. Empty description lowers confidence, but the name and server context strongly suggest active execution.

From the tool's definition Tool name 'scan_ports' on a server described as providing network diagnostics capabilities; description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs scan_ports 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 scan_ports, this is the rule to start with:

scan_ports Rate-limited

scan_ports 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": {
    "scan_ports": {
      "limits": [
        {
          "counter": "scan_ports_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 scan_ports call is checked against it from then on.

FAQ

Questions about scan_ports

What does the scan_ports tool do? +

scan_ports 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 scan_ports? +

Register the Allcanuse MCP server in PolicyLayer and add a rule for scan_ports: 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 scan_ports? +

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

Can I rate-limit scan_ports? +

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

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

scan_ports 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

run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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