Compute correlation between branches
AI agents call compute_correlation to retrieve information from CERN ROOT MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Computing correlation is a statistical analysis operation that retrieves data from ROOT file branches and performs mathematical calculations. It does not create, modify, delete, or execute external operations—it only reads and analyzes existing data. This clearly falls under the Read category with low severity, as misuse would only result in access to statistical information without side effects.
From the tool's definition Tool computes correlation between branches in ROOT files, which involves reading and analyzing data without modification.
Attacks that exploit this kind of access
Compute correlation between branches. It is categorised as a Read tool in the CERN ROOT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CERN ROOT MCP Server MCP server in PolicyLayer and add a rule for compute_correlation: 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 CERN ROOT MCP Server. Nothing to install.
compute_correlation 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 compute_correlation 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 compute_correlation. 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.
compute_correlation is provided by the CERN ROOT MCP Server MCP server (mohamedelashri/root-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 →