AI agents call get_protein_interactions to retrieve information from Gwas without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing biological data (protein-protein interactions) from a public database without creating, modifying, deleting, or executing any external operations. It is a straightforward read operation typical of bioinformatics research tools. The risk is minimal as it accesses publicly available, read-only data.
From the tool's definition Tool description states 'Get protein-protein interaction network' and 'Shows what proteins interact', indicating data retrieval with no modification or deletion. The STRING database is a public bioinformatics resource for querying protein interactions.
Attacks that exploit this kind of access
Get protein-protein interaction network from STRING database. Shows what proteins interact with your protein of interest. It is categorised as a Read tool in the Gwas MCP Server, which means it retrieves data without modifying state.
Register the Gwas MCP server in PolicyLayer and add a rule for get_protein_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 Gwas. Nothing to install.
get_protein_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_protein_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_protein_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_protein_interactions is provided by the Gwas MCP server (muslus/gwas-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 →