Low Risk

get_variant_info

get_variant_info

How to control get_variant_info ↓

What get_variant_info does on gnomAD MCP Server

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

Low Risk

Why get_variant_info needs a policy

The tool retrieves variant information from the gnomAD genomic database. Like all named 'get_*' operations on this server, it appears to be a read-only query that returns existing data without modifying, deleting, or executing arbitrary code. The genomic/medical context poses minimal misuse risk—querying variant frequencies and annotations cannot directly harm systems or finances.

From the tool's definition Tool name 'get_variant_info' and server context indicate data retrieval from gnomAD database. Sibling tools (get_clinvar_variant_info, get_gene_info, get_metadata, get_region_info, etc.) are all read-only query operations.

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

How to control get_variant_info

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

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

get_variant_info 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 gnomAD MCP Server — 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 get_variant_info

What does the get_variant_info tool do? +

get_variant_info. It is categorised as a Read tool in the gnomAD MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_variant_info? +

Register the gnomAD MCP Server MCP server in PolicyLayer and add a rule for get_variant_info: 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 gnomAD MCP Server. Nothing to install.

What risk level is get_variant_info? +

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

Can I rate-limit get_variant_info? +

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

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

get_variant_info is provided by the gnomAD MCP Server MCP server (koido/gnomad-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every gnomAD MCP Server tool call.

Start from gnomAD MCP Server, 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.

12 gnomAD MCP Server 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.