Queue a model pull (no-op executor in MVP)
AI agents invoke ollama_pull to trigger actions in Promethean OS MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool queues a model pull operation, which triggers an external operation (downloading/pulling an AI model). Even though the description notes it's a 'no-op executor in MVP', the intended behavior is to initiate a network/download operation. The 'no-op' qualifier lowers confidence since it may have no real effect currently, but the design intent is to execute an external pull operation.
From the tool's definition Queue a model pull (no-op executor in MVP)
Attacks that exploit this kind of access
Queue a model pull (no-op executor in MVP). It is categorised as a Execute tool in the Promethean OS MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Promethean OS MCP server in PolicyLayer and add a rule for ollama_pull: 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 Promethean OS MCP. Nothing to install.
ollama_pull is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ollama_pull 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_pull. 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_pull is provided by the Promethean OS MCP server (octave-commons/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 →