get_associated_diseases_by_drug_name
Retrieve the list of diseases associated with a specific drug based on clinical trial data or post-marketed drugs.
This record as markdown: /tools/gentel-lab-origenemcp/get-associated-diseases-by-drug-name.md
What get_associated_diseases_by_drug_name does on OrigeneMCP
AI agents call get_associated_diseases_by_drug_name to retrieve information from OrigeneMCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_associated_diseases_by_drug_name is rated Low
This tool queries a biomedical database to fetch disease associations linked to a drug. It has no side effects, does not modify data, execute code, delete records, or move money. It is a straightforward informational lookup, consistent with other sibling tools on this server (check_*, get_*, query_* variants) that retrieve clinical and genomic data.
From the tool's definition Tool name contains 'get' and description states 'Retrieve the list of diseases associated with a specific drug' — a passive data retrieval operation with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs get_associated_diseases_by_drug_name safely
PolicyLayer is an MCP gateway: it sits between your AI agents and OrigeneMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_associated_diseases_by_drug_name, this is the rule to start with:
get_associated_diseases_by_drug_name is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect OrigeneMCP, apply this rule, and every get_associated_diseases_by_drug_name call is checked against it from then on.
Questions about get_associated_diseases_by_drug_name
Retrieve the list of diseases associated with a specific drug based on clinical trial data or post-marketed drugs. It is categorised as a Read tool in the OrigeneMCP MCP Server, which means it retrieves data without modifying state.
Register the Origene MCP server in PolicyLayer and add a rule for get_associated_diseases_by_drug_name: 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 OrigeneMCP. Nothing to install.
get_associated_diseases_by_drug_name 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_associated_diseases_by_drug_name 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_associated_diseases_by_drug_name. 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_associated_diseases_by_drug_name is provided by the Origene MCP server (gentel-lab/origenemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Origene, and thousands of servers like it.
This server
Across the catalogue