get_correlation_data
AI agents call get_correlation_data to retrieve information from Lumenore Analytics MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description, the naming convention and server context strongly indicate this tool queries correlations within analytics data—a retrieval operation with no side effects. The sibling tools all perform Read operations (getting metadata, trends, predictions, outliers). Correlation analysis is a passive analytical operation that computes relationships between data variables without modifying state.
From the tool's definition Tool name 'get_correlation_data' follows the established pattern of sibling tools (get_trend_data, get_prediction_data, get_outlier_data) that retrieve and analyze data.
Attacks that exploit this kind of access
get_correlation_data. It is categorised as a Read tool in the Lumenore Analytics MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lumenore Analytics MCP Server MCP server in PolicyLayer and add a rule for get_correlation_data: 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 Lumenore Analytics MCP Server. Nothing to install.
get_correlation_data 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_correlation_data 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_correlation_data. 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_correlation_data is provided by the Lumenore Analytics MCP Server MCP server (lumenore-platform/lumenore-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 →