List all available Ollama models installed locally. Returns model names, sizes, and modification dates.
AI agents call ollama_list 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 a read-only operation that queries and returns metadata about installed models. It has no capability to modify, delete, execute code, or trigger external operations. The blast radius of misuse is minimal—an AI agent could at most enumerate available models, which presents no security risk.
From the tool's definition Tool name 'ollama_list' and description 'List all available Ollama models installed locally. Returns model names, sizes, and modification dates' indicate a query operation that retrieves information without modification or side effects.
Documented attack patterns abuse exactly the kind of access ollama_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ollama MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for ollama_list:
{
"version": "1",
"default": "deny",
"tools": {
"ollama_list": {}
}
}ollama_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all available Ollama models installed locally. Returns model names, sizes, and modification dates. 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 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 Ollama MCP Server. 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 Ollama MCP Server MCP server (rawveg/ollama-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 Ollama MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 Ollama MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.