Fetch the full aggregated annotation object for a single disease id. Accepts MONDO ("MONDO:0015967"), DOID ("DOID:9351"), OMIM ("OMIM:125853") and other supported ontology ids. Returns cross-referenced data including MONDO ontology (labels, synonyms, xrefs, parents/children), gene-disease associa...
AI agents call disease 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 |
|---|---|---|---|
id | string | Yes | A disease id such as "MONDO:0015967", "DOID:9351", or "OMIM:125853". |
fields | string | — | Comma-separated list of annotation fields to return (default: all fields). |
Parameters from the server's own tool schema.
This tool retrieves and aggregates existing disease-related data from multiple sources (MONDO, DisGeNET, HPO, CTD) based on provided ontology identifiers. It performs no create, modify, delete, or execute operations. The data returned is informational and read-only.
From the tool's definition Tool description states 'Fetch the full aggregated annotation object' and 'Returns cross-referenced data' with no mention of modification, deletion, or execution. The verb 'Fetch' and 'Returns' indicate pure data retrieval with no side effects.
Attacks that exploit this kind of access
Fetch the full aggregated annotation object for a single disease id. Accepts MONDO ("MONDO:0015967"), DOID ("DOID:9351"), OMIM ("OMIM:125853") and other supported ontology ids. Returns cross-referenced data including MONDO ontology (labels, synonyms, xrefs, parents/children), gene-disease associations from DisGeNET, phenotypes from HPO, and chemical-disease relationships from CTD. Resolve a name to an id first via the "query" tool. It is categorised as a Read tool in the Mcp Mydisease MCP Server, which means it retrieves data without modifying state.
disease accepts 2 parameters: id, fields. Required: id. 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 disease: 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.
disease 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 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. 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 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 →