Calculates the cardiovascular disease (CVD) 10-year risk based on the Pooled Cohort Equations and lifetime risk prediction tools.
AI agents call calculate_cvd_risk to retrieve information from Cardiovascular Disease without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure computational tool that takes patient clinical parameters as input and returns a calculated risk score. It retrieves or computes information from existing data without creating, modifying, deleting, or executing external operations. It has no side effects on the patient record or clinical system.
From the tool's definition Tool name 'calculate_cvd_risk' and description states it 'Calculates the cardiovascular disease (CVD) 10-year risk based on the Pooled Cohort Equations'.
Attacks that exploit this kind of access
Calculates the cardiovascular disease (CVD) 10-year risk based on the Pooled Cohort Equations and lifetime risk prediction tools. It is categorised as a Read tool in the Cardiovascular Disease MCP Server, which means it retrieves data without modifying state.
Register the Cardiovascular Disease MCP server in PolicyLayer and add a rule for calculate_cvd_risk: 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 Cardiovascular Disease. Nothing to install.
calculate_cvd_risk 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 calculate_cvd_risk 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 calculate_cvd_risk. 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.
calculate_cvd_risk is provided by the Cardiovascular Disease MCP server (jamesvdinh/cardiovascular-disease-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 →