Copy a model
AI agents use ollama_cp to create or update resources in Unified MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unified MCP Server environment.
Copying a model creates a new copy of an existing model, which is a reversible write operation. It does not delete or overwrite existing data, execute code, or involve financial transactions. The blast radius is medium since it could consume significant storage resources if misused.
From the tool's definition Copy a model
Attacks that exploit this kind of access
Copy a model. It is categorised as a Write tool in the Unified MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Unified MCP Server MCP server in PolicyLayer and add a rule for ollama_cp: 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 Unified MCP Server. Nothing to install.
ollama_cp is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ollama_cp 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_cp. 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_cp is provided by the Unified MCP Server MCP server (qingyunyupan/ollama-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 →