ctx_doctor

Diagnose context-mode installation. Runs all checks server-side and returns a plain-text status report with [OK]/[FAIL]/[WARN] prefixes (renderer-safe across MCP clients). No CLI execution needed.

ServerContext Mode
CategoryRead

How to control ctx_doctor ↓

WHAT IT DOES

What ctx_doctor does on Context Mode

AI agents call ctx_doctor to retrieve information from Context Mode without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

THE RISK

Low Risk

Why ctx_doctor needs a policy

The tool performs diagnostic checks and returns a status report. It is read-only in nature — gathering and reporting system state without modifying data, executing external commands, or causing side effects. The description explicitly notes 'No CLI execution needed', further reinforcing its read-only classification. Low severity as it only surfaces diagnostic information.

From the tool's definition Diagnose context-mode installation. Runs all checks server-side and returns a plain-text status report with [OK]/[FAIL]/[WARN] prefixes. No CLI execution needed.

Documented attack patterns abuse exactly the kind of access ctx_doctor gives an agent:

POLICY

How to control ctx_doctor

PolicyLayer is an MCP gateway — it sits between your AI agents and Context Mode, and nothing reaches the server without passing your rules. This is the rule we recommend for ctx_doctor:

policy.json

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

ctx_doctor is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Context Mode — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Context Mode tools

Destructive ctx_purge DESTRUCTIVE: permanently delete indexed content. Cannot be undone. Requires confirm:true a Execute ctx_batch_execute Run multiple commands in ONE call. Every command Execute ctx_execute Run code in a sandboxed subprocess.${RB} Languages: ${PB}. Think-in-Code \u2014 the core Execute ctx_execute_file Read a file into a sandboxed FILE_CONTENT variable and run code over it. Only what you con Execute ctx_insight Opens the context-mode Insight dashboard in the browser \u2014 a dashboard launcher for se Execute ctx_upgrade Upgrade context-mode to the latest version. Returns a shell command to execute. You MUST r Write ctx_index Store content in a searchable knowledge base (BM25 over FTS5). Splits markdown by headings Write ctx_fetch_and_index Fetches URL content, converts HTML to markdown (JSON is chunked by key paths, plain text i

All 11 Context Mode tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about ctx_doctor

What does the ctx_doctor tool do? +

Diagnose context-mode installation. Runs all checks server-side and returns a plain-text status report with [OK]/[FAIL]/[WARN] prefixes (renderer-safe across MCP clients). No CLI execution needed. It is categorised as a Read tool in the Context Mode MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ctx_doctor? +

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

What risk level is ctx_doctor? +

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

Can I rate-limit ctx_doctor? +

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

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

ctx_doctor is provided by the Context Mode MCP server (mksglu/context-mode). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Context Mode tool call.

Start from Context Mode, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

11 Context Mode tools catalogued and risk-classified — across an index of 43,000+ MCP servers.