create_auth_server
A write tool on the API-Central MCP server.
This record as markdown: /tools/secure-ssid-centralmcp/create-auth-server.md
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 create_auth_server is rated Medium
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
The rule that runs create_auth_server safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API-Central, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_auth_server, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect API-Central, apply this rule, and every create_auth_server call is checked against it from then on.
Questions about create_auth_server
create_auth_server is a write tool on the API-Central MCP 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.
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.
create_auth_server is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
More on API-Central, and thousands of servers like it.
This server
Across the catalogue