Show how the codebase executes: top entry points and their call traces. Returns scored entry points with BFS call-path traces showing which functions are called in sequence and whether the flow crosses community boundaries. Args: top_n: Number of top entry points to trace (default 10). max_depth:...
AI agents call get_execution_flows to retrieve information from Repowise without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs static analysis of code execution patterns by tracing call paths and entry points. It reads codebase metadata (functions, call relationships, community boundaries) to construct execution flow diagrams but does not execute code, modify files, delete data, or trigger external operations. The parameters (top_n, max_depth, entry_point) control query scope, not side effects.
From the tool's definition Tool description states it 'Show[s] how the codebase executes' and 'Returns scored entry points with BFS call-path traces' — purely analytical operations that retrieve and display execution flow information without modifying, executing, or deleting code.
Documented attack patterns abuse exactly the kind of access get_execution_flows gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Repowise, and nothing reaches the server without passing your rules. This is the rule we recommend for get_execution_flows:
{
"version": "1",
"default": "deny",
"tools": {
"get_execution_flows": {}
}
}get_execution_flows 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.
Show how the codebase executes: top entry points and their call traces. Returns scored entry points with BFS call-path traces showing which functions are called in sequence and whether the flow crosses community boundaries. Args: top_n: Number of top entry points to trace (default 10). max_depth: Max trace depth per flow (default 8). entry_point: Trace from a specific symbol (overrides top_n scoring). repo: Usually omitted. It is categorised as a Read tool in the Repowise MCP Server, which means it retrieves data without modifying state.
Register the Repowise MCP server in PolicyLayer and add a rule for get_execution_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 Repowise. Nothing to install.
get_execution_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 get_execution_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 get_execution_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.
get_execution_flows is provided by the Repowise MCP server (repowise-dev/repowise). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 Repowise tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
19 Repowise tools catalogued and risk-classified — across an index of 42,500+ MCP servers.