graph_explorer

THE RISK

Low Risk

Why graph_explorer needs a policy

The tool opens an interactive explorer for viewing graph data within the MCP client. This is a read/visualization operation with no indication of write, execute, or destructive capabilities. Confidence is slightly reduced because 'interactive' could imply some write capabilities, but the description emphasizes exploration/viewing.

From the tool's definition Open an interactive Graph Explorer inside the MCP client

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

POLICY

How to control graph_explorer

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

policy.json

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

graph_explorer 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 CodeGraph — 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 CodeGraph tools

Destructive decay_and_prune Run temporal memory maintenance: decay relevance scores for old entities and optionally pr Execute trigger_reindex Trigger a reindex of the codebase. Supports incremental (changed files only) or full mode. Execute query_graph Run a raw Cypher query against the code graph. Use with caution - read-only queries only. Write ingest_conversation Ingest a multi-turn conversation into the knowledge graph. Runs the full episodic pipeline Write store_entity Store an entity in the knowledge graph. Deduplicates by text+type — if an entity with the Write store_fact Extract entities and relationships from natural language text using an LLM, then store the Write store_relationship Store a relationship between two entities in the knowledge graph. Entities are referenced Write add Ingest any content into the knowledge graph. Accepts file paths (PDF, DOCX, HTML, CSV,

All 18 CodeGraph 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 graph_explorer

What does the graph_explorer tool do? +

Open an interactive Graph Explorer inside the MCP client. It is categorised as a Read tool in the CodeGraph MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on graph_explorer? +

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

What risk level is graph_explorer? +

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

Can I rate-limit graph_explorer? +

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

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

graph_explorer is provided by the CodeGraph MCP server (phoenixrr2113/codebase-graph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every CodeGraph tool call.

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

CHECK YOUR STACK →