port_scan · MCP Server Foundation Template MCP

WHAT IT DOES

What port_scan does on MCP Server Foundation Template

AI agents invoke port_scan to trigger actions in MCP Server Foundation Template. 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 IT NEEDS A POLICY

Why port_scan needs a policy

Port scanning actively probes remote hosts/networks to discover open ports and services. This is an external operation with real-world effects (network traffic sent to targets, potential legal/policy implications). It fits 'Execute' as it triggers external operations. Severity is high because an AI agent could misuse it to scan arbitrary hosts, constituting unauthorized network reconnaissance.

From the tool's definition Tool name 'port_scan' — description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

port_scan Rate-limited

port_scan 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": {
    "port_scan": {
      "limits": [
        {
          "counter": "port_scan_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Server Foundation Template, so you can run agents against it safely.

FAQ

Questions about port_scan

What does the port_scan tool do? +

port_scan. It is categorised as a Execute tool in the MCP Server Foundation Template MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on port_scan? +

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

What risk level is port_scan? +

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

Can I rate-limit port_scan? +

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

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

port_scan is provided by the MCP Server Foundation Template MCP server (joeyheath65/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.