High Risk →

diagnose

Run a self-diagnosis of the MCP server's environment: Node version, resolved PATH, provider CLI presence and versions, key env vars. Returns a structured report and a human-readable summary. Read-only; never spawns LLM calls.

Part of the Ask Ollama server.

diagnose can trigger actions in Ask Ollama, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE ASK OLLAMA →

Free to start. No card required.

AI agents invoke diagnose to trigger processes or run actions in Ask Ollama. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

diagnose can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "diagnose": {
      "limits": [
        {
          "counter": "diagnose_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Ask Ollama policy for all 5 tools.

Get this rule live on your own Ask Ollama server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY ASK OLLAMA →

These attack patterns abuse exactly the kind of access diagnose gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so diagnose only ever does what you allow.

SECURE ASK OLLAMA →

Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the diagnose tool do? +

Run a self-diagnosis of the MCP server's environment: Node version, resolved PATH, provider CLI presence and versions, key env vars. Returns a structured report and a human-readable summary. Read-only; never spawns LLM calls.. It is categorised as a Execute tool in the Ask Ollama MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on diagnose? +

Register the Ask Ollama MCP server in PolicyLayer and add a rule for diagnose: 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 Ask Ollama. Nothing to install.

What risk level is diagnose? +

diagnose is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit diagnose? +

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

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

diagnose is provided by the Ask Ollama MCP server (ask-ollama-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ask Ollama tool call.

Deterministic rules across all 5 Ask Ollama tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.