Get CPU and memory usage information from the device.
AI agents call get_resource_usage to retrieve information from Netmiko MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves monitoring data (CPU and memory statistics) from a network device via SSH. It is a read-only operation with no side effects, no code execution, and no data modification. The blast radius of misuse is minimal—an agent could only gather operational data about the device. It does not create, modify, delete, or execute arbitrary commands.
From the tool's definition Tool name 'get_resource_usage' and description 'Get CPU and memory usage information from the device' indicate a retrieval operation that queries device metrics without modifying, executing code, or affecting system state.
Attacks that exploit this kind of access
Get CPU and memory usage information from the device. It is categorised as a Read tool in the Netmiko MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Netmiko MCP Server MCP server in PolicyLayer and add a rule for get_resource_usage: 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 Netmiko MCP Server. Nothing to install.
get_resource_usage 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_resource_usage 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_resource_usage. 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_resource_usage is provided by the Netmiko MCP Server MCP server (owen123-lang/netmiko_mcp_server). 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 →