Low Risk

get_file_symbols

Retrieve all symbols (classes, functions, etc.) defined in a specific file.

How to control get_file_symbols ↓

What get_file_symbols does on GraphHub

AI agents call get_file_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 get_file_symbols needs a policy

This tool retrieves static code metadata (symbol definitions like classes and functions) from a file. It has no side effects, no code execution capability, and no data modification or deletion. The operation is purely informational, consistent with other Read category tools like 'find_duplicates' and 'find_dead_code' on the same server.

From the tool's definition Tool name 'get_file_symbols' and description 'Retrieve all symbols' indicate a read-only operation that queries and returns metadata about code structure without modifying, executing, or deleting anything.

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

How to control get_file_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 get_file_symbols:

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

get_file_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 get_file_symbols

What does the get_file_symbols tool do? +

Retrieve all symbols (classes, functions, etc.) defined in a specific file. 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 get_file_symbols? +

Register the GraphHub MCP server in PolicyLayer and add a rule for get_file_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 get_file_symbols? +

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

Can I rate-limit get_file_symbols? +

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

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

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