monitor_system_resources
AI agents call monitor_system_resources to retrieve information from Observability MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Monitoring and observability tools are non-destructive read operations that query system state, resource utilization, and health metrics. There is no indication this tool modifies, executes commands, or deletes data. The empty description is a minor confidence reducer, but the name and server context (observability/monitoring) strongly suggest a passive read operation with minimal blast radius if misused.
From the tool's definition Tool name 'monitor_system_resources' implies passive observation of system state. Sibling tools include 'collect_performance_metrics', 'check_stack_status', and other monitoring/observability functions that retrieve telemetry data without modification.
Attacks that exploit this kind of access
monitor_system_resources. It is categorised as a Read tool in the Observability MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Observability MCP Server MCP server in PolicyLayer and add a rule for monitor_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 Observability MCP Server. Nothing to install.
monitor_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 monitor_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 monitor_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.
monitor_system_resources is provided by the Observability MCP Server MCP server (sandraschi/observability-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 →