Low Risk

fetch_graph_data

Internal companion — fetches project-scoped graph nodes and edges for the graph_explorer App UI canvas.

How to control fetch_graph_data ↓

What fetch_graph_data does on CodeGraph

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

Low Risk

Why fetch_graph_data needs a policy

This tool retrieves and queries existing graph structure data (nodes and edges) to populate a UI visualization. It has no side effects, does not execute code, does not modify or delete data, and does not commit financial obligations. It is a straightforward data retrieval operation fitting the Read category.

From the tool's definition Tool description states it 'fetches project-scoped graph nodes and edges' — a retrieval operation with no modification, deletion, or execution capabilities. The verb 'fetches' and the context of serving data to a UI canvas indicate read-only behavior.

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

How to control fetch_graph_data

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 fetch_graph_data:

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

fetch_graph_data 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 CodeGraph — 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 fetch_graph_data

What does the fetch_graph_data tool do? +

Internal companion — fetches project-scoped graph nodes and edges for the graph_explorer App UI canvas. 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 fetch_graph_data? +

Register the CodeGraph MCP server in PolicyLayer and add a rule for fetch_graph_data: 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 fetch_graph_data? +

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

Can I rate-limit fetch_graph_data? +

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

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

fetch_graph_data 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.

Free to start. No card required.

18 CodeGraph 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.