test_port_connectivity · MCP Log Analyzer MCP: Risk & Policy

WHAT IT DOES

What test_port_connectivity does on MCP Log Analyzer

AI agents invoke test_port_connectivity to trigger actions in MCP Log Analyzer. 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 test_port_connectivity needs a policy

Testing port connectivity requires actively sending network packets to remote endpoints, which constitutes executing an external network operation. This is not a passive read; it triggers real network activity that could be detected as scanning, trigger security alerts, or probe sensitive infrastructure. It spans Execute rather than Read because it has observable side effects on external systems.

From the tool's definition 'Test connectivity to specific ports' — actively initiates network connections to external hosts/ports

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

test_port_connectivity Rate-limited

test_port_connectivity 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": {
    "test_port_connectivity": {
      "limits": [
        {
          "counter": "test_port_connectivity_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 Log Analyzer, so you can run agents against it safely.

FAQ

Questions about test_port_connectivity

What does the test_port_connectivity tool do? +

Test connectivity to specific ports. It is categorised as a Execute tool in the MCP Log Analyzer MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on test_port_connectivity? +

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

What risk level is test_port_connectivity? +

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

Can I rate-limit test_port_connectivity? +

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

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

test_port_connectivity is provided by the MCP Log Analyzer MCP server (sedwardstx/demomcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.