Get protein-protein, genetic, or regulatory interactions for a gene or protein.
AI agents call get_interactions 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 query/retrieval operation against a genomics database (WormBase) that returns pre-existing interaction information. There are no side effects, data modifications, code execution, financial transactions, or destructive actions. The blast radius of misuse is minimal—an agent could retrieve irrelevant interaction data but cannot modify, delete, or execute anything.
From the tool's definition Tool is named 'get_interactions' and retrieves interaction data (protein-protein, genetic, regulatory) for genes/proteins.
Attacks that exploit this kind of access
Get protein-protein, genetic, or regulatory interactions for a gene or protein. 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_interactions: 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_interactions 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_interactions 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_interactions. 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_interactions 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 →