// MCP TOOL REFERENCE

kg_diagnostic

ServerPersonal Kg
CategoryExecute

WHAT IT DOES

What kg_diagnostic does on Personal Kg

AI agents invoke kg_diagnostic to trigger actions in Personal Kg. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

THE RISK

High Risk

Why kg_diagnostic needs a policy

While the tool's primary purpose is diagnostic/read (querying knowledge graph data for debugging), it executes an external side effect by opening a browser window. This qualifies as Execute since it triggers an external operation whose effect depends on the environment.

From the tool's definition 'Opens in browser' — the tool triggers an external operation (launching a browser) and generates/renders an HTML dashboard, going beyond simple data retrieval.

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

POLICY

How to control kg_diagnostic

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "kg_diagnostic": {
      "limits": [
        {
          "counter": "kg_diagnostic_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

kg_diagnostic stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

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

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Personal Kg tools

Write kg_capture Primary tool for capturing knowledge nodes. Use this to record decisions, progress updates Write kg_capture_session Captures session summaries with structured metadata. Use at the end of work sessions to re Write kg_link_session Creates a relationship between a session node and another knowledge node. Use to explicitl Write kg_resolve_question Marks a question as resolved by linking it to a decision, insight, or other node that answ Write kg_update_node Updates an existing knowledge node. Use to modify content, tags, importance, or visibility Read kg_session_warmup Start every session with this tool! Loads comprehensive context about your project includi Other kg_admin Unified admin tool for maintenance operations. Supports: Read kg_analyze Unified analysis tool. Supports:

All 18 Personal Kg tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Personal Kg → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about kg_diagnostic

What does the kg_diagnostic tool do? +

Generate a diagnostic HTML dashboard for debugging knowledge graph context selection, search results, and node visibility. Opens in browser to help understand why certain nodes are included/excluded from context. It is categorised as a Execute tool in the Personal Kg MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on kg_diagnostic? +

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

What risk level is kg_diagnostic? +

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

Can I rate-limit kg_diagnostic? +

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

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

kg_diagnostic is provided by the Personal Kg MCP server (tomschell/personal-kg-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Personal Kg tool call.

Start from Personal Kg, 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.

18 Personal Kg tools catalogued and risk-classified — across an index of 43,000+ MCP servers.