get_running_config

Get the full running configuration of an Aruba device.

Server HPE Aruba Networking Central MCP Server the-otner/aruba-mcp
Category Read
Risk class Low
Parameters 00 required

What get_running_config does on HPE Aruba Networking Central MCP Server

AI agents call get_running_config to retrieve information from HPE Aruba Networking Central MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_running_config needs a policy

This tool retrieves/queries the running configuration of a network device. It performs a read operation with no side effects, data modification, or destructive action. Severity is medium rather than low because running configurations contain sensitive network topology, security policies, and operational details that could be misused if retrieved by an unauthorized agent, but the tool itself causes no harm when…

From the tool's definition Tool name 'get_running_config' and description 'Get the full running configuration of an Aruba device' indicate retrieval of configuration data with no modification or execution.

Questions about get_running_config

What does the get_running_config tool do? +

Get the full running configuration of an Aruba device. It is categorised as a Read tool in the HPE Aruba Networking Central MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_running_config? +

Register the HPE Aruba Networking Central MCP Server MCP server in PolicyLayer and add a rule for get_running_config: 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 HPE Aruba Networking Central MCP Server. Nothing to install.

What risk level is get_running_config? +

get_running_config is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_running_config? +

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

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

get_running_config is provided by the HPE Aruba Networking Central MCP Server MCP server (the-otner/aruba-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.