configure_high_availability
A write tool on the API-Central MCP server.
This record as markdown: /tools/secure-ssid-centralmcp/configure-high-availability.md
What configure_high_availability does on API-Central
AI agents use configure_high_availability 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 configure_high_availability is rated Medium
The tool name strongly suggests modifying high-availability configuration for network infrastructure (consistent with HPE Aruba Central's domain). Configuration changes are reversible writes. Severity is high because HA misconfigurations could cause network outages or failover issues affecting multiple systems, though not financial or destructive.
From the tool's definition Tool name 'configure_high_availability' indicates modification of network infrastructure high-availability settings.
Attacks that exploit this kind of access
The rule that runs configure_high_availability 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 configure_high_availability, this is the rule to start with:
configure_high_availability 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 configure_high_availability call is checked against it from then on.
Questions about configure_high_availability
configure_high_availability 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 configure_high_availability: 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.
configure_high_availability 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 configure_high_availability 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 configure_high_availability. 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.
configure_high_availability 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