find_flows_from_source_call_to_sink_call
AI agents call find_flows_from_source_call_to_sink_call to retrieve information from Joern MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool analyzes data flow between source and sink calls in a codebase. This is a static analysis query operation that retrieves and traces information through code—characteristic of code analysis tools. It does not modify, execute, or delete code; it only inspects and reports findings. The low severity reflects that misuse would yield analytical results rather than cause system damage or data loss.
From the tool's definition Tool name 'find_flows_from_source_call_to_sink_call' and sibling tools like 'find_flows_from_method_params_to_sink_method', 'get_call_code_by_id', 'get_calls_in_method_by_method_full_name', 'get_class_full_name_by_id', 'get_class_methods_by_class_full_name',…
Documented attack patterns abuse exactly the kind of access find_flows_from_source_call_to_sink_call gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Joern MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for find_flows_from_source_call_to_sink_call:
{
"version": "1",
"default": "deny",
"tools": {
"find_flows_from_source_call_to_sink_call": {}
}
}find_flows_from_source_call_to_sink_call 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.
find_flows_from_source_call_to_sink_call. It is categorised as a Read tool in the Joern MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Joern MCP Server MCP server in PolicyLayer and add a rule for find_flows_from_source_call_to_sink_call: 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 Joern MCP Server. Nothing to install.
find_flows_from_source_call_to_sink_call 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 find_flows_from_source_call_to_sink_call 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 find_flows_from_source_call_to_sink_call. 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.
find_flows_from_source_call_to_sink_call is provided by the Joern MCP Server MCP server (sfncat/mcp-joern). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 Joern MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 Joern MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.