central_run_network_test · Central MCP: Risk & Policy

WHAT IT DOES

What central_run_network_test does on Central

AI agents invoke central_run_network_test to trigger actions in Central. 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 central_run_network_test needs a policy

This tool executes network tests against HPE Aruba infrastructure, which constitutes running operations with side effects that depend on arguments (e.g., which network segment, device, or test type to run). While network tests are typically non-destructive read-adjacent operations, the 'run' verb and execution nature place this in Execute category rather than Read.

From the tool's definition Tool name 'central_run_network_test' indicates execution of network diagnostic operations. The verb 'run' combined with 'network_test' suggests active triggering of external network operations whose effects depend on runtime arguments and network state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

central_run_network_test Rate-limited

central_run_network_test 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": {
    "central_run_network_test": {
      "limits": [
        {
          "counter": "central_run_network_test_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 Central, so you can run agents against it safely.

FAQ

Questions about central_run_network_test

What does the central_run_network_test tool do? +

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

How do I enforce a policy on central_run_network_test? +

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

What risk level is central_run_network_test? +

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

Can I rate-limit central_run_network_test? +

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

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

central_run_network_test is provided by the Central MCP server (karthikskumar98/central-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.