Low Risk

changed_symbols

List the symbols in files changed by the current branch (or working tree / staged diff). Each entry includes a direct-caller count and risk bucket so agents know where breakage is most likely. Use this before committing or when reviewing a PR.

How to control changed_symbols ↓

What changed_symbols does on GraphHub

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

Low Risk

Why changed_symbols needs a policy

This tool retrieves and displays information about symbols in changed files along with metadata about their callers and risk levels. It has no capability to modify, delete, execute, or trigger external operations. The stated purpose—helping agents understand where breakage is likely before committing—confirms it is purely informational. No side effects occur from calling this tool.

From the tool's definition Tool description states it 'List[s] the symbols in files changed' and provides 'direct-caller count and risk bucket' information.

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

How to control changed_symbols

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

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

changed_symbols 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 GraphHub — 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 changed_symbols

What does the changed_symbols tool do? +

List the symbols in files changed by the current branch (or working tree / staged diff). Each entry includes a direct-caller count and risk bucket so agents know where breakage is most likely. Use this before committing or when reviewing a PR. It is categorised as a Read tool in the GraphHub MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on changed_symbols? +

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

What risk level is changed_symbols? +

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

Can I rate-limit changed_symbols? +

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

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

changed_symbols is provided by the GraphHub MCP server (slnquangtran/graph-hub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GraphHub tool call.

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

32 GraphHub 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.