Get the AST outline of a file (classes, functions, interfaces, constants).
AI agents call get_file_structure to retrieve information from Headless Codebase Indexer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure read operation that parses and returns abstract syntax tree metadata about code structure. It has no side effects, cannot modify files, execute code, or delete data. The blast radius of misuse is minimal—an agent could learn about code structure but cannot cause damage. It aligns with sibling tools (get_definition, get_references, semantic_search) which are all read-only inspection operations.
From the tool's definition The tool retrieves an 'AST outline' of a file, listing structural elements (classes, functions, interfaces, constants) without modifying any code. The description explicitly indicates data retrieval only.
Attacks that exploit this kind of access
Get the AST outline of a file (classes, functions, interfaces, constants). It is categorised as a Read tool in the Headless Codebase Indexer MCP Server, which means it retrieves data without modifying state.
Register the Headless Codebase Indexer MCP server in PolicyLayer and add a rule for get_file_structure: 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 Headless Codebase Indexer. Nothing to install.
get_file_structure is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_file_structure 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.
Set action: deny in the PolicyLayer policy for get_file_structure. 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.
get_file_structure is provided by the Headless Codebase Indexer MCP server (y1hanh/codebase-indexer-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →