Low Risk

full_risk_report

Generate a comprehensive genetic disease risk report covering all analyzed conditions: cancer, cardiovascular, neurological, metabolic, autoimmune, and more.

How to control full_risk_report ↓

What full_risk_report does on Openpgx

AI agents call full_risk_report to retrieve information from Openpgx without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why full_risk_report needs a policy

The tool generates a report by querying structured pharmacogenomic and disease risk data, which is fundamentally a retrieval operation (Read category). Although the output contains sensitive health information that could influence medical decisions, the tool itself performs no write, delete, execute, or financial operations.

From the tool's definition "Generate a comprehensive genetic disease risk report" - this tool queries and retrieves analyzed genetic risk data; "covering all analyzed conditions: cancer, cardiovascular, neurological, metabolic, autoimmune, and more" indicates it performs data retrieval…

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

How to control full_risk_report

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 full_risk_report:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "full_risk_report": {}
  }
}

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

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about full_risk_report

What does the full_risk_report tool do? +

Generate a comprehensive genetic disease risk report covering all analyzed conditions: cancer, cardiovascular, neurological, metabolic, autoimmune, and more. 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 full_risk_report? +

Register the Openpgx MCP server in PolicyLayer and add a rule for full_risk_report: 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 full_risk_report? +

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

Can I rate-limit full_risk_report? +

Yes. Add a rate_limit block to the full_risk_report 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 full_risk_report completely? +

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

full_risk_report 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.

Free to start. No card required.

15 Openpgx tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.