test_port · Windows Operations MCP: Risk & Policy

WHAT IT DOES

What test_port does on Windows Operations MCP

AI agents invoke test_port to trigger actions in Windows Operations MCP. 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 needs a policy

Based on the server description mentioning 'network testing' capabilities, 'test_port' likely performs a network port connectivity test (e.g., Test-NetConnection or similar). This triggers an external network operation whose effects depend on the target host and port arguments, placing it in the Execute category.

From the tool's definition Tool name 'test_port' on a server that includes 'network testing' in its description. The description is empty, lowering confidence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

test_port Rate-limited

test_port 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": {
      "limits": [
        {
          "counter": "test_port_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 Windows Operations MCP, so you can run agents against it safely.

FAQ

Questions about test_port

What does the test_port tool do? +

test_port. It is categorised as a Execute tool in the Windows Operations MCP 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? +

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

What risk level is test_port? +

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

Can I rate-limit test_port? +

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

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

test_port is provided by the Windows Operations MCP server (sandraschi/windows-operations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.