get_ollama_list
AI agents call get_ollama_list to retrieve information from Ollama_MCP_Guidance without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix conventionally indicates retrieval without modification. The tool appears to return a list from Ollama (likely models or running instances) similar to sibling 'list_models' and 'get_running_models' tools. No side effects or state changes are implied. Severity is low because listing available models or API information poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'get_ollama_list' uses 'get' verb, indicating data retrieval. Sibling tools include 'list_models', 'get_api_doc_section', 'get_ollama_version', 'get_running_models', and 'get_started_guide', all of which are read-only queries.
Attacks that exploit this kind of access
get_ollama_list. It is categorised as a Read tool in the Ollama_MCP_Guidance MCP Server, which means it retrieves data without modifying state.
Register the Ollama_MCP_Guidance MCP server in PolicyLayer and add a rule for get_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_Guidance. Nothing to install.
get_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 get_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 get_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.
get_ollama_list is provided by the Ollama_MCP_Guidance MCP server (shadovvsinger/ollama_mcp_guidance). 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 →