AI agents call get_execution_flows to retrieve information from Srclight without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs introspection on code structure (call graphs) to understand execution paths. It has no side effects, makes no modifications, executes no code, and deletes nothing. It is purely informational retrieval, consistent with other sibling tools like 'find_imports', 'find_pattern', and 'codebase_map' which are all Read operations in a deep code indexing service.
From the tool's definition The tool 'get_execution_flows' retrieves and traces execution flows through the call graph. The verb 'Get' and the action of tracing/navigating call graphs are read-only operations that query code structure without modifying, executing, or deleting anything.
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 Srclight, 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.
Get traced execution flows through the call graph. It is categorised as a Read tool in the Srclight MCP Server, which means it retrieves data without modifying state.
Register the Srclight 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 Srclight. 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 Srclight MCP server (srclight/srclight). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 42 Srclight tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
42 Srclight tools catalogued and risk-classified — across an index of 42,500+ MCP servers.