두 트랙 간의 상관관계를 분석합니다
AI agents call analyze_correlation to retrieve information from VitalDB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs correlation analysis on medical datasets, which is a read-only statistical computation. It examines relationships between data variables without creating, modifying, deleting, or executing external operations. The broader server context (VitalDB for medical data exploration and analysis) and sibling tools all support this classification as data retrieval and analysis functions.
From the tool's definition Tool name 'analyze_correlation' and sibling tools (find_cases, get_case_info, plot_distribution, plot_heatmap) indicate data analysis and querying.
Attacks that exploit this kind of access
두 트랙 간의 상관관계를 분석합니다. It is categorised as a Read tool in the VitalDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the VitalDB MCP Server MCP server in PolicyLayer and add a rule for analyze_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 VitalDB MCP Server. Nothing to install.
analyze_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 analyze_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 analyze_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.
analyze_correlation is provided by the VitalDB MCP Server MCP server (yejelim/vitaldb-mcp-server). 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 →