Get one genome by MGnify accession (e.g.
AI agents call mgnify_get_genome to retrieve information from MGnify 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 simple query/retrieval operation that fetches genome data from the MGnify database. It has no side effects, does not modify data, does not execute code or commands, and does not perform destructive or financial operations. The blast radius of misuse is minimal—an agent could only retrieve existing genome data. Classified as Read with low severity.
From the tool's definition Tool name 'mgnify_get_genome' and description indicate retrieval of a single genome resource by accession identifier. The 'get' verb and context of querying MGnify metagenomics API with no mention of modifications, deletions, or external execution.
Attacks that exploit this kind of access
Get one genome by MGnify accession (e.g. It is categorised as a Read tool in the MGnify MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MGnify MCP Server MCP server in PolicyLayer and add a rule for mgnify_get_genome: 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 MGnify MCP Server. Nothing to install.
mgnify_get_genome 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 mgnify_get_genome 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 mgnify_get_genome. 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.
mgnify_get_genome is provided by the MGnify MCP Server MCP server (mgs-sails/mgnify-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 →