Filter variants by pathogenicity threshold. Efficiently identifies pathogenic variants from large lists. Perfect for: VCF filtering, prioritizing clinical variants. Example:
AI agents call batch_pathogenicity_filter to retrieve information from AlphaGenome MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs filtering and querying on genomic variant data based on pathogenicity scores. It retrieves and organizes existing data according to specified criteria but does not create, modify, delete, or execute arbitrary operations. The operation is read-only with no side effects. Even in the context of a genomic analysis platform, filtering is fundamentally a data retrieval operation.
From the tool's definition Tool description states 'Filter variants by pathogenicity threshold' and 'Efficiently identifies pathogenic variants from large lists.' The example use cases 'VCF filtering, prioritizing clinical variants' indicate data retrieval and categorization without…
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Filter variants by pathogenicity threshold. Efficiently identifies pathogenic variants from large lists. Perfect for: VCF filtering, prioritizing clinical variants. Example:. It is categorised as a Read tool in the AlphaGenome MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AlphaGenome MCP Server MCP server in PolicyLayer and add a rule for batch_pathogenicity_filter: 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 AlphaGenome MCP Server. Nothing to install.
batch_pathogenicity_filter 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 batch_pathogenicity_filter 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 batch_pathogenicity_filter. 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.
batch_pathogenicity_filter is provided by the AlphaGenome MCP Server MCP server (taehojo/alphagenome-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 →