get_cpu_memory_detail
AI agents call get_cpu_memory_detail 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 name indicates it retrieves system resource details (CPU/memory) from network devices. This is a passive read operation with no side effects on configuration, data, or state. The empty description lowers confidence slightly, but the naming convention clearly suggests a monitoring/diagnostic read rather than any action that could modify or delete resources.
From the tool's definition Tool name 'get_cpu_memory_detail' indicates retrieval of CPU and memory information without modification. No description provided, but the name strongly suggests a read-only query operation.
Attacks that exploit this kind of access
get_cpu_memory_detail. 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_cpu_memory_detail: 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_cpu_memory_detail 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_cpu_memory_detail 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_cpu_memory_detail. 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_cpu_memory_detail 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 →