Analyze code structure using tree-sitter.
AI agents call analyze_structure to retrieve information from Code Intelligence MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs static code analysis to understand structure and organization. Tree-sitter is a parser generator that reads source code and builds syntax trees for analysis purposes. No data is created, modified, deleted, or executed. It is a read-only information retrieval operation with minimal blast radius if misused by an agent.
From the tool's definition Tool description states it 'Analyze[s] code structure using tree-sitter' — a parsing operation that retrieves and examines code without modification. No side effects or state changes implied.
Attacks that exploit this kind of access
Analyze code structure using tree-sitter. It is categorised as a Read tool in the Code Intelligence MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Code Intelligence MCP Server MCP server in PolicyLayer and add a rule for analyze_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 Code Intelligence MCP Server. Nothing to install.
analyze_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 analyze_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 analyze_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.
analyze_structure is provided by the Code Intelligence MCP Server MCP server (tech-spoke/llm-helper). 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 →