Get the full causal network for a project as nodes and edges — suitable for D3/Mermaid graph visualization
AI agents call get_causal_graph to retrieve information from Semantic Context MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns graph structure data (nodes and edges) for visualization purposes. It performs a query operation that has no side effects, does not modify data, does not execute code or commands, and does not delete or move resources. It is a straightforward read operation that falls squarely within the Read category.
From the tool's definition Tool name 'get_causal_graph' and description 'Get the full causal network for a project as nodes and edges — suitable for D3/Mermaid graph visualization' indicate retrieval and querying of existing graph data.
Attacks that exploit this kind of access
Get the full causal network for a project as nodes and edges — suitable for D3/Mermaid graph visualization. It is categorised as a Read tool in the Semantic Context MCP MCP Server, which means it retrieves data without modifying state.
Register the Semantic Context MCP server in PolicyLayer and add a rule for get_causal_graph: 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 Semantic Context MCP. Nothing to install.
get_causal_graph 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_causal_graph 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_causal_graph. 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_causal_graph is provided by the Semantic Context MCP server (semanticintent/semantic-wake-intelligence-mcp). 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 →