Get detailed AST node information at a specific cursor position. Perfect for debugging and precise analysis.\n\nExamples:\n• Debug syntax errors: get_node_at_position(15, 23) to understand what
AI agents call get_node_at_position to retrieve information from Tree-Hugger-JS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries Abstract Syntax Tree (AST) node information at specified positions in code. It is purely informational with no side effects—it does not execute, modify, delete, or transform code. This is a classic Read operation: it fetches data to support analysis activities.
From the tool's definition Tool name is 'get_node_at_position' and description states it 'Get[s] detailed AST node information at a specific cursor position' with purpose for 'debugging and precise analysis'. No modification, deletion, or execution of code is described.
Attacks that exploit this kind of access
Get detailed AST node information at a specific cursor position. Perfect for debugging and precise analysis.\n\nExamples:\n• Debug syntax errors: get_node_at_position(15, 23) to understand what. It is categorised as a Read tool in the Tree-Hugger-JS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tree-Hugger-JS MCP Server MCP server in PolicyLayer and add a rule for get_node_at_position: 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-Hugger-JS MCP Server. Nothing to install.
get_node_at_position 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_node_at_position 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_node_at_position. 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_node_at_position is provided by the Tree-Hugger-JS MCP Server MCP server (qckfx/tree-hugger-js-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 →