Search MyDisease.info for diseases by free-text name or fielded query. Returns matching hits, each keyed by a MONDO disease id (e.g. "MONDO:0015967") with the best-matching ontology and annotation keys. Use this to resolve a disease name to canonical ontology ids before calling the "disease" tool...
AI agents call query to retrieve information from Mcp Mydisease without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
size | number | — | Number of hits to return, 1-1000 (default 10). |
query | string | Yes | Free-text disease name (e.g. "diabetes") or a fielded query (e.g. "mondo.label:asthma"). |
fields | string | — | Comma-separated list of annotation fields to return (default: all fields). |
Parameters from the server's own tool schema.
This tool performs read-only queries against a disease dataset. It retrieves and returns information with no side effects, no data modification, and no ability to execute code or trigger external operations. It is a straightforward search/lookup function that falls clearly into the Read category.
From the tool's definition Tool description explicitly states 'Search MyDisease.info for diseases' and 'Returns matching hits'. The description emphasizes querying and resolving disease names without any capability to modify, delete, or execute operations.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
Search MyDisease.info for diseases by free-text name or fielded query. Returns matching hits, each keyed by a MONDO disease id (e.g. "MONDO:0015967") with the best-matching ontology and annotation keys. Use this to resolve a disease name to canonical ontology ids before calling the "disease" tool. Free text like "diabetes" or "asthma" works; fielded queries like "mondo.label:asthma" or "disgenet.xrefs.disease_name:..." narrow the search. It is categorised as a Read tool in the Mcp Mydisease MCP Server, which means it retrieves data without modifying state.
query accepts 3 parameters: size, query, fields. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Mydisease MCP server in PolicyLayer and add a rule for query: 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 Mcp Mydisease. Nothing to install.
query 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 query 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 query. 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.
query is provided by the Mcp Mydisease MCP server (https://gateway.pipeworx.io/mydisease/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 →