Check Ollama service status (running, version, GPU)
AI agents call ollama_status to retrieve information from ML Lab MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and reports status information about the Ollama service—whether it is running, its version, and GPU availability. It has no side effects, does not modify state, and does not execute arbitrary operations. It is a pure information retrieval function, fitting the Read category with low severity since querying service status poses minimal risk even if misused.
From the tool's definition Tool name 'ollama_status' and description 'Check Ollama service status (running, version, GPU)' indicate a query/monitoring operation that retrieves system state without modification.
Attacks that exploit this kind of access
Check Ollama service status (running, version, GPU). It is categorised as a Read tool in the ML Lab MCP MCP Server, which means it retrieves data without modifying state.
Register the ML Lab MCP server in PolicyLayer and add a rule for ollama_status: 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 ML Lab MCP. Nothing to install.
ollama_status 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 ollama_status 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 ollama_status. 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.
ollama_status is provided by the ML Lab MCP server (pushpullcommitpush/ml-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 →