ruvllm_status

Get ruvllm-wasm availability and initialization status. Use when sending every prompt to the Anthropic API is wrong because you need local inference — air-gapped environments, MicroLoRA-fine-tuned per-task adapters, or sub-cent per-call cost. For general Claude work native Task is the right call.

SERVERClaude Flow SOURCEclaude-flow

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-ruvnet-claude-flow/ruvllm-status.md

WHAT IT DOES

What ruvllm_status does on Claude Flow

AI agents call ruvllm_status to retrieve information from Claude Flow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why ruvllm_status is rated Low

This tool retrieves status information about a local inference runtime (ruvllm-wasm). It performs a pure read operation—checking availability and initialization state—without modifying any state, executing commands, or triggering side effects. The high confidence reflects the explicit 'Get' verb and status-query semantics in both name and description.

From the tool's definition Tool name 'ruvllm_status' and description 'Get ruvllm-wasm availability and initialization status' indicate a query/retrieval operation with no side effects.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ruvllm_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ruvllm_status, this is the rule to start with:

ruvllm_status Allowed

ruvllm_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ruvllm_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every ruvllm_status call is checked against it from then on.

FAQ

Questions about ruvllm_status

What does the ruvllm_status tool do? +

How do I enforce a policy on ruvllm_status? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for ruvllm_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 Claude Flow. Nothing to install.

What risk level is ruvllm_status? +

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

Can I rate-limit ruvllm_status? +

Yes. Add a rate_limit block to the ruvllm_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 ruvllm_status completely? +

Set action: deny in the PolicyLayer policy for ruvllm_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 ruvllm_status? +

ruvllm_status is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Flow, and thousands of servers like it.

This server

All 496 Claude Flow tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →