AI agents call cross_layer_flow_map to retrieve information from Sfgraph without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to generate or retrieve a map/graph representation of cross-layer flows within Salesforce orgs. The 'map' designation and sibling tools focused on analysis (dead_code_audit, explain_code, find_similar) suggest read-only introspection. However, confidence is moderate due to the truncated description ('USE THIS for any' is incomplete), which prevents full assessment of potential side effects or scope.
From the tool's definition Tool name 'cross_layer_flow_map' and description 'USE THIS for any' suggest a visualization or mapping function.
Attacks that exploit this kind of access
USE THIS for any. It is categorised as a Read tool in the Sfgraph MCP Server, which means it retrieves data without modifying state.
Register the Sfgraph MCP server in PolicyLayer and add a rule for cross_layer_flow_map: 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 Sfgraph. Nothing to install.
cross_layer_flow_map 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 cross_layer_flow_map 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 cross_layer_flow_map. 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.
cross_layer_flow_map is provided by the Sfgraph MCP server (ryanstark24/sfgraph). 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 →