Get information about a scientific paper/publication including authors, abstract, and associated genes.
AI agents call get_paper 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 is a data retrieval operation that queries and returns information about scientific papers without creating, modifying, deleting, or executing any operations. It fits the Read category as a straightforward lookup/fetch operation with no destructive or side-effect-inducing capability.
From the tool's definition Tool retrieves publication metadata (authors, abstract, associated genes) from the WormBase database with no modification capabilities. The verb 'Get' and read-only nature of fetching paper information confirms no side effects.
Attacks that exploit this kind of access
Get information about a scientific paper/publication including authors, abstract, and associated genes. 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_paper: 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_paper 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_paper 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_paper. 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_paper 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 →