Low Risk

get_symbols

Extract symbols from a file. Args: project: Project name file_path: Path to the file symbol_types: Types of symbols to extract (functions, classes, imports, etc.) Returns: Dictionary of symbols by type

How to control get_symbols ↓

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

Low Risk

This is a read-only operation that queries and retrieves code metadata (symbol information) from a file without modifying, deleting, or executing any code. It performs static analysis to extract structural information, which is characteristic of Read category tools. The low severity reflects minimal risk—misuse would only expose code structure information already present in the codebase.

From the tool's definition The tool 'get_symbols' extracts symbols from a file and returns a dictionary of symbols by type. The description explicitly states it retrieves/queries code structure (functions, classes, imports) with 'no side effects' implied by the extraction operation.

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

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

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

get_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 Tree Sitter — 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.

Go deeper

What does the get_symbols tool do? +

Extract symbols from a file. Args: project: Project name file_path: Path to the file symbol_types: Types of symbols to extract (functions, classes, imports, etc.) Returns: Dictionary of symbols by type. It is categorised as a Read tool in the Tree Sitter MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_symbols? +

Register the Tree Sitter MCP server in PolicyLayer and add a rule for get_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 Tree Sitter. Nothing to install.

What risk level is get_symbols? +

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

Can I rate-limit get_symbols? +

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

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

get_symbols is provided by the Tree Sitter MCP server (wrale/mcp-server-tree-sitter). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Tree Sitter tool call.

Deterministic rules across all 26 Tree Sitter tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

26 Tree Sitter tools catalogued and risk-classified — across an index of 42,500+ 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.