Get information about any WormBase entity type. Use this for entity types not covered by specific tools.
AI agents call get_entity to retrieve information from WormBase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data from the WormBase database without side effects. The verb 'Get' and the context of querying a read-only scientific database (C. elegans genomics) confirm it performs only Read operations. No capability to create, modify, delete, or execute external operations is indicated.
From the tool's definition Tool name 'get_entity' and description 'Get information about any WormBase entity type' indicate data retrieval with no modification. All sibling tools (get_disease, get_expression, get_gene, etc.) are read operations querying a genomics database.
Attacks that exploit this kind of access
Get information about any WormBase entity type. Use this for entity types not covered by specific tools. It is categorised as a Read tool in the WormBase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WormBase MCP Server MCP server in PolicyLayer and add a rule for get_entity: 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 WormBase MCP Server. Nothing to install.
get_entity 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 get_entity 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 get_entity. 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.
get_entity is provided by the WormBase MCP Server MCP server (wormbase/wormbase-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 →