AI agents call disease_bridge to retrieve information from Sniff Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the server's stated purpose of providing genomic data and allele frequencies, and the pattern of sibling tools that are all informational reads (disease_lookup, disease_links, gene_summary, breed_summary), this tool most likely queries or retrieves disease-related genomic information without side effects. No creation, modification, deletion, code execution, or financial operations are indicated.
From the tool's definition Tool name 'disease_bridge' appears on a genomics information server (Sniff Atlas) with sibling tools that are all read-only queries (ask, breed_summary, gene_summary, disease_lookup, disease_links).
Attacks that exploit this kind of access
disease_bridge. It is categorised as a Read tool in the Sniff Mcp MCP Server, which means it retrieves data without modifying state.
Register the Sniff MCP server in PolicyLayer and add a rule for disease_bridge: 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 Sniff Mcp. Nothing to install.
disease_bridge 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 disease_bridge 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 disease_bridge. 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.
disease_bridge is provided by the Sniff MCP server (https://mcp.sniff.world/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
disease_bridge is one line of Sniff's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →