List all detected execution flows — entry points traced through the call graph. Each flow has a name, entry point, and ordered steps.
AI agents call flows to retrieve information from code-intel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns static analysis data (execution flows, entry points, call graph traces) with no side effects, data modification, code execution, or destructive actions. It fits the Read category: retrieves/queries data for analysis purposes only.
From the tool's definition Tool description states 'List all detected execution flows' — a read-only operation that retrieves and displays call graph analysis without modifying code or triggering execution.
Attacks that exploit this kind of access
List all detected execution flows — entry points traced through the call graph. Each flow has a name, entry point, and ordered steps. It is categorised as a Read tool in the code-intel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the code-intel MCP Server MCP server in PolicyLayer and add a rule for flows: 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-intel MCP Server. Nothing to install.
flows 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 flows 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 flows. 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.
flows is provided by the code-intel MCP Server MCP server (vohongtho/code-intel-platform). 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 →