check_risk

THE RISK

Low Risk

Why check_risk needs a policy

This tool retrieves and queries existing genetic risk information from structured health data based on user genome data. It performs no modification, deletion, or external execution—merely reading and returning risk assessments for specified conditions (cancer, alzheimer).

From the tool's definition Tool name 'check_risk' and description 'Check your genetic risk for a specific disease or condition' indicate a query/retrieval operation.

Documented attack patterns abuse exactly the kind of access check_risk gives an agent:

POLICY

How to control check_risk

PolicyLayer is an MCP gateway — it sits between your AI agents and Openpgx, and nothing reaches the server without passing your rules. This is the rule we recommend for check_risk:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_risk": {}
  }
}

check_risk is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Openpgx — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Openpgx tools

Write save_drug_research Save pharmacogenomic research from web search as a local study. Validates the data, caches Write upload_genome_chunk FOR PROGRAMMATIC MCP CLIENTS ONLY (not for LLM agents). LLM agents: use get_upload_command Write upload_genome_start FOR PROGRAMMATIC MCP CLIENTS ONLY (not for LLM agents). LLM agents: use get_upload_command Read check_medication Check how your genes affect a medication. Supports brand names ( Read compare_medications Compare two medications head-to-head based on your genetic profile. Supports brand names. Read diagnostic_all Generate the most comprehensive genomic report available. Runs ALL modules at once: pharma Read full_pgx_report Generate a complete pharmacogenomic report with all your genes, phenotypes, and affected m Read full_report Generate a complete genomic intelligence report covering all three modules: medications (P

All 15 Openpgx tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about check_risk

What does the check_risk tool do? +

Check your genetic risk for a specific disease or condition. Supports: cancer, alzheimer. It is categorised as a Read tool in the Openpgx MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_risk? +

Register the Openpgx MCP server in PolicyLayer and add a rule for check_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 Openpgx. Nothing to install.

What risk level is check_risk? +

check_risk is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_risk? +

Yes. Add a rate_limit block to the check_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.

How do I block check_risk completely? +

Set action: deny in the PolicyLayer policy for check_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.

What MCP server provides check_risk? +

check_risk is provided by the Openpgx MCP server (open-pgx/openpgx). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Openpgx tool call.

Start from Openpgx, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →