Trace downstream execution from a known workspace symbol to see what it calls and which files it reaches before modifying logic. Resolve path with code.find_symbol first. Language filters: ${SUPPORTED_LANGUAGE_FILTERS}.
AI agents call code.trace_flow to retrieve information from Navigation Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
code.trace_flow retrieves and queries call relationships and file dependencies without creating, modifying, executing, or deleting any code or data. It is a static analysis tool for codebase inspection, analogous to sibling tools (find_symbol, search_text, inspect_tree) that are all read-only navigation aids.
From the tool's definition Tool description states it traces 'downstream execution from a known workspace symbol to see what it calls and which files it reaches' — purely observational activities.
Attacks that exploit this kind of access
Trace downstream execution from a known workspace symbol to see what it calls and which files it reaches before modifying logic. Resolve path with code.find_symbol first. Language filters: ${SUPPORTED_LANGUAGE_FILTERS}. It is categorised as a Read tool in the Navigation Agent MCP Server, which means it retrieves data without modifying state.
Register the Navigation Agent MCP server in PolicyLayer and add a rule for code.trace_flow: 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 Navigation Agent. Nothing to install.
code.trace_flow 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 code.trace_flow 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 code.trace_flow. 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.
code.trace_flow is provided by the Navigation Agent MCP server (j0k3r-dev-rgl/navigation-agent-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 →