Get current system resource usage
AI agents call get_system_resources to retrieve information from Modular MCP Server & Client without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reports current system resource statistics (CPU, memory, disk, etc.) with no side effects, no code execution, and no data modification. It is purely informational, characteristic of Read category tools. Severity is low because even if an AI agent calls it repeatedly or maliciously, the worst outcome is resource consumption for monitoring, not unauthorized access or system compromise.
From the tool's definition Tool name 'get_system_resources' and description 'Get current system resource usage' indicate a query operation that retrieves system metrics without modification or execution of commands.
Attacks that exploit this kind of access
Get current system resource usage. It is categorised as a Read tool in the Modular MCP Server & Client MCP Server, which means it retrieves data without modifying state.
Register the Modular MCP Server & Client MCP server in PolicyLayer and add a rule for get_system_resources: 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 Modular MCP Server & Client. Nothing to install.
get_system_resources 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_resources 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_resources. 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_resources is provided by the Modular MCP Server & Client MCP server (jackmichaud/modular-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 →