Get detailed information about a specific node in the plan. Returns the node\
AI agents call get_node_info to retrieve information from Overture without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about a plan node without modifying, executing, or deleting any data. It is a straightforward read operation consistent with query/get/fetch semantics. The low severity reflects minimal risk even if misused—an AI agent retrieving plan node details poses no destructive, financial, or code execution risk.
From the tool's definition Tool name 'get_node_info' and description 'Get detailed information about a specific node in the plan. Returns the node...' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_node_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Overture, and nothing reaches the server without passing your rules. This is the rule we recommend for get_node_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_node_info": {}
}
}get_node_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed information about a specific node in the plan. Returns the node\. It is categorised as a Read tool in the Overture MCP Server, which means it retrieves data without modifying state.
Register the Overture MCP server in PolicyLayer and add a rule for get_node_info: 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 Overture. Nothing to install.
get_node_info 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_info 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_info. 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_info is provided by the Overture MCP server (sixhq/overture). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 Overture tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 Overture tools catalogued and risk-classified — across an index of 42,500+ MCP servers.