Retrieve detailed metadata about a specific installed Ollama model.
AI agents call ollama_show_model to retrieve information from Ollama-Omega without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward data retrieval operation. It queries and returns information about an existing model without creating, modifying, deleting, or executing anything. The action is informational only, making it a Read category tool. Severity is low because metadata retrieval poses minimal risk even if misused by an AI agent—it cannot alter system state, trigger external operations, or cause data loss.
From the tool's definition Tool retrieves detailed metadata about a specific installed Ollama model. Verbs: 'Retrieve' and 'metadata' indicate a read-only query operation with no side effects or data modification.
Attacks that exploit this kind of access
Retrieve detailed metadata about a specific installed Ollama model. It is categorised as a Read tool in the Ollama-Omega MCP Server, which means it retrieves data without modifying state.
Register the Ollama-Omega MCP server in PolicyLayer and add a rule for ollama_show_model: 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-Omega. Nothing to install.
ollama_show_model 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_show_model 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_show_model. 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_show_model is provided by the Ollama-Omega MCP server (vrtxomega/ollama-omega). 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 →