Check system resources and compatibility
AI agents call system_resource_check to retrieve information from Ollama MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs passive system monitoring/diagnostics by checking resources (CPU, memory, disk, GPU, etc.) and compatibility status. It has no side effects, does not execute commands, does not modify state, and merely returns informational data. This is a straightforward Read operation with minimal risk if misused—worst case, repeated calls waste compute cycles.
From the tool's definition Tool name 'system_resource_check' and description 'Check system resources and compatibility' indicate a read-only query operation that retrieves system information without modifying or executing anything.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Check system resources and compatibility. It is categorised as a Read tool in the Ollama MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Ollama MCP Server MCP server in PolicyLayer and add a rule for system_resource_check: 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 Ollama MCP Server. Nothing to install.
system_resource_check 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 system_resource_check 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 system_resource_check. 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.
system_resource_check is provided by the Ollama MCP Server MCP server (paolodalprato/ollama-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 →