New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

models_status

Check Ollama status: running, port, GPU, model count.

SERVERYaver SOURCEyaver-cli
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/models-status.md

What models_status does on Yaver

AI agents call models_status 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.

Why models_status is rated Low

This tool only retrieves and reports the current status of Ollama (a local LLM framework), similar to status checks or health probes. It has no side effects, does not modify data, execute code, or trigger operations. The information returned is read-only diagnostic data. Severity is low because misuse would only expose system state information without enabling harmful actions.

From the tool's definition Tool name 'models_status' and description 'Check Ollama status: running, port, GPU, model count' indicates a read-only query operation that retrieves state information without modification or execution of external commands.

Questions about models_status

What does the models_status tool do? +

Check Ollama status: running, port, GPU, model count. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on models_status? +

Register the Yaver MCP server in PolicyLayer and add a rule for models_status: 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.

What risk level is models_status? +

models_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit models_status? +

Yes. Add a rate_limit block to the models_status 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.

How do I block models_status completely? +

Set action: deny in the PolicyLayer policy for models_status. 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.

What MCP server provides models_status? +

models_status 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Yaver's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.