create_auth_server · API-Central MCP: Risk & Policy

WHAT IT DOES

What create_auth_server does on API-Central

AI agents use create_auth_server to create or update resources in API-Central — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your API-Central environment.

WHY IT NEEDS A POLICY

Why create_auth_server needs a policy

Creating authentication servers modifies network configuration and security posture reversibly. This falls under Write category rather than Execute because it appears to be a configuration creation action rather than executing arbitrary code. However, severity is elevated to 'high' because misuse could compromise network authentication mechanisms, affecting access control across the infrastructure.

From the tool's definition Tool name 'create_auth_server' indicates creation of authentication infrastructure. The description is empty, limiting direct evidence, but the name and context within HPE Aruba Central (network operations platform) suggest this tool creates or configures…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_auth_server Rate-limited

create_auth_server stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_auth_server": {
      "limits": [
        {
          "counter": "create_auth_server_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 create_auth_server

What does the create_auth_server tool do? +

create_auth_server. It is categorised as a Write tool in the API-Central MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_auth_server? +

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

create_auth_server is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_auth_server? +

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

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

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