aos_s_traceroute · API-Central MCP: Risk & Policy

WHAT IT DOES

What aos_s_traceroute does on API-Central

AI agents invoke aos_s_traceroute to trigger actions in API-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 aos_s_traceroute needs a policy

This tool executes a command on network infrastructure (an AOS-S switch). While traceroute itself is non-destructive and read-oriented in nature, it falls under Execute rather than Read because it triggers an active operation on a remote system whose scope and impact depend on user-supplied arguments (the target host).

From the tool's definition The tool description states it 'Run[s] a traceroute from an AOS-S switch', which is a network diagnostic command execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

aos_s_traceroute Rate-limited

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

FAQ

Questions about aos_s_traceroute

What does the aos_s_traceroute tool do? +

Run a traceroute from an AOS-S switch (async, polls ~60s). It is categorised as a Execute tool in the API-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 aos_s_traceroute? +

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

What risk level is aos_s_traceroute? +

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

Can I rate-limit aos_s_traceroute? +

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

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

aos_s_traceroute is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.