Map coordinates between different genome assemblies
AI agents call map_assembly 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 pure data retrieval and transformation tool. It takes genomic coordinates from one assembly version and returns their corresponding positions in another assembly version. No data is created, modified, deleted, or executed—it is a read-only query against reference genome mapping data.
From the tool's definition Tool name 'map_assembly' and description 'Map coordinates between different genome assemblies' indicate a coordinate transformation/lookup operation.
Attacks that exploit this kind of access
Map coordinates between different genome assemblies. 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 map_assembly: 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.
map_assembly 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 map_assembly 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 map_assembly. 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.
map_assembly 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.
map_assembly is one line of Ensembl MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →