get_system_info
AI agents call get_system_info 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.
The tool appears to retrieve system information without modifying data or triggering state changes. While the description is empty (lowering confidence slightly), the naming convention 'get_' is a strong indicator of a Read operation. In the context of an HPE Aruba Networking Central platform, querying system information has minimal blast radius and no destructive or financial implications.
From the tool's definition Tool name 'get_system_info' indicates retrieval of system information. No description provided, but the name pattern and context within a network management platform suggests a query operation.
Attacks that exploit this kind of access
get_system_info. 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.
Register the HPE Aruba Networking Central MCP Server MCP server in PolicyLayer and add a rule for get_system_info: 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.
get_system_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_system_info 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 get_system_info. 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.
get_system_info 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.
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 →