Low Risk

index_diagnosis

인덱싱 문제를 진단하고 해결합니다. 실제 메모리 vs 인덱싱된 메모리 불일치 문제 분석

How to control index_diagnosis ↓

What index_diagnosis does on Work Memory MCP Server

AI agents call index_diagnosis to retrieve information from Work Memory MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why index_diagnosis needs a policy

This tool performs diagnostic analysis of indexing problems by comparing actual memory against indexed memory state. It retrieves and analyzes data to identify discrepancies but does not modify, create, delete, or execute external operations. The primary function is reading and understanding the current state of the memory index system, making it a Read category tool.

From the tool's definition Tool name 'index_diagnosis' and description indicating it 'diagnoses and resolves indexing issues' and 'analyzes actual memory vs indexed memory discrepancies.' The description uses verbs 'diagnose' and 'analyze' which are inspection and analysis operations…

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

How to control index_diagnosis

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "index_diagnosis": {}
  }
}

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

  1. Create a free account and register Work Memory MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about index_diagnosis

What does the index_diagnosis tool do? +

인덱싱 문제를 진단하고 해결합니다. 실제 메모리 vs 인덱싱된 메모리 불일치 문제 분석. It is categorised as a Read tool in the Work Memory MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on index_diagnosis? +

Register the Work Memory MCP Server MCP server in PolicyLayer and add a rule for index_diagnosis: 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 Work Memory MCP Server. Nothing to install.

What risk level is index_diagnosis? +

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

Can I rate-limit index_diagnosis? +

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

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

index_diagnosis is provided by the Work Memory MCP Server MCP server (moontmsai/work-memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Work Memory MCP Server tool call.

Start from Work Memory MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

24 Work Memory MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.