test_aaa · API-Central MCP: Risk & Policy

WHAT IT DOES

What test_aaa does on API-Central

AI agents invoke test_aaa 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 test_aaa needs a policy

This tool triggers an active network test operation — executing an AAA (Authentication, Authorization, Accounting) connectivity test from a network device. It performs an external operation with real network effects (sending authentication requests to AAA servers), runs asynchronously, and involves polling, indicating it initiates and monitors an active process rather than simply reading existing data.

From the tool's definition Test AAA connectivity from an AP or CX switch (async, polls ~60s)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

test_aaa Rate-limited

test_aaa 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_aaa": {
      "limits": [
        {
          "counter": "test_aaa_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 test_aaa

What does the test_aaa tool do? +

Test AAA connectivity from an AP or CX 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 test_aaa? +

Register the API-Central MCP server in PolicyLayer and add a rule for test_aaa: 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 test_aaa? +

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

Can I rate-limit test_aaa? +

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

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

test_aaa 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.