This record as markdown: /tools/io-github-kivanccakmak-yaver/models-pull.md
What models_pull does on Yaver
AI agents call models_pull to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Model name (e.g. llama3.2, codellama, nomic-embed-text) |
Parameters from the server's own tool schema.
Why models_pull is rated Low
Even though models_pull only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs models_pull safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For models_pull, this is the rule to start with:
models_pull is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every models_pull call is checked against it from then on.
Questions about models_pull
Download an Ollama model. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
models_pull accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for models_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 Yaver. Nothing to install.
models_pull 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 models_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 models_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.
models_pull is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue