Get analytics on causal relationships for a project
AI agents call get_causality_stats 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 is a read-only operation that retrieves analytics about causal relationships within a project. There are no side effects, no data modifications, no code execution, and no irreversible actions. The tool fits the Read category definition: 'retrieves or queries data; no side effects'.
From the tool's definition Tool name and description indicate data retrieval: 'Get analytics on causal relationships' — this queries and returns statistics/analytics data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Get analytics on causal relationships for a project. 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_causality_stats: 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_causality_stats 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_causality_stats 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_causality_stats. 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_causality_stats 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 →