AI agents call get_trace_node_details to retrieve information from Openl without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves trace debugging information (parameters, context, results, errors) from an already-captured trace. It is a read-only diagnostic query with no side effects on the OpenL system state or data. The node IDs come from another tool (openl_get_trace_nodes), confirming this is passive inspection of trace output.
From the tool's definition Tool name 'get_trace_node_details' and description 'Get detailed trace node including parameters, context, result, and errors' indicate a query/retrieval operation with no modification, creation, or deletion of data.
Attacks that exploit this kind of access
Get detailed trace node including parameters, context, result, and errors. Node IDs come from openl_get_trace_nodes. It is categorised as a Read tool in the Openl MCP Server, which means it retrieves data without modifying state.
Register the Openl MCP server in PolicyLayer and add a rule for get_trace_node_details: 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 Openl. Nothing to install.
get_trace_node_details 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_trace_node_details 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_trace_node_details. 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_trace_node_details is provided by the Openl MCP server (openl-mcp-server). 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 →