List all models in Ollama
AI agents call ollama_list 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 performs a read-only operation to enumerate or fetch metadata about models stored in Ollama. It has no side effects, does not execute code, modify data, or consume resources beyond querying. The blast radius of misuse is minimal—an agent could only learn what models are available, posing no security or operational risk.
From the tool's definition Tool name 'ollama_list' and description 'List all models in Ollama' indicate a query operation that retrieves information about available models without modifying, executing, or deleting any data.
Attacks that exploit this kind of access
List all models in Ollama. 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_list: 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_list 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_list 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_list. 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_list 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 →