AI agents call lookup_variant_clinvar to retrieve information from Pgx without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves variant clinical significance information from ClinVar, a public database of genetic variants. It performs a query operation that returns information without modifying, executing code, deleting, or committing financial transactions. The blast radius of misuse is minimal—an agent might retrieve irrelevant or erroneous variant data, but cannot harm systems or data integrity.
From the tool's definition Tool name 'lookup_variant_clinvar' indicates a query/lookup operation against ClinVar database; sibling tools like 'get_dosing_guideline', 'get_drug_gene_interactions', 'get_variant_frequency', and 'search_gene_variants_clinvar' all clearly perform read-only…
Attacks that exploit this kind of access
lookup_variant_clinvar. It is categorised as a Read tool in the Pgx MCP Server, which means it retrieves data without modifying state.
Register the Pgx MCP server in PolicyLayer and add a rule for lookup_variant_clinvar: 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 Pgx. Nothing to install.
lookup_variant_clinvar 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 lookup_variant_clinvar 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 lookup_variant_clinvar. 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.
lookup_variant_clinvar is provided by the Pgx MCP server (julius-schmidt/mcp-pharmacogenomics). 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 →