Search taxonomy by name
AI agents call search_taxonomy_by_name to retrieve information from Ensembl MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a data retrieval tool that searches for and returns taxonomic information based on name input. It performs no creation, modification, deletion, or execution of code/commands. The blast radius of misuse is minimal—an agent could only retrieve unwanted taxonomic data, with no side effects on the underlying genomic database or external systems.
From the tool's definition Tool name 'search_taxonomy_by_name' and description 'Search taxonomy by name' indicate a query operation that retrieves taxonomic classification data without modification.
Attacks that exploit this kind of access
Search taxonomy by name. It is categorised as a Read tool in the Ensembl MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Ensembl MCP Server MCP server in PolicyLayer and add a rule for search_taxonomy_by_name: 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 Ensembl MCP Server. Nothing to install.
search_taxonomy_by_name 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 search_taxonomy_by_name 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 search_taxonomy_by_name. 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.
search_taxonomy_by_name is provided by the Ensembl MCP Server MCP server (munch-group/ensembl-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 →