get_disease_locations_by_name
Retrieve the locations of a specific disease.
This record as markdown: /tools/gentel-lab-origenemcp/get-disease-locations-by-name.md
What get_disease_locations_by_name does on OrigeneMCP
AI agents call get_disease_locations_by_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_disease_locations_by_name is rated Low
This tool queries biomedical data to return disease location information. It performs no data modification, deletion, code execution, or financial transaction. It is a straightforward information retrieval operation with minimal blast radius if misused by an AI agent—it would only return factual epidemiological or genetic location data.
From the tool's definition Tool name is 'get_disease_locations_by_name' and description states 'Retrieve the locations of a specific disease.' The verb 'Retrieve' and absence of mutation, modification, or execution language indicate a read-only query operation.
Attacks that exploit this kind of access
The rule that runs get_disease_locations_by_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_disease_locations_by_name, this is the rule to start with:
get_disease_locations_by_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_disease_locations_by_name call is checked against it from then on.
Questions about get_disease_locations_by_name
Retrieve the locations of a specific disease. 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_disease_locations_by_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_disease_locations_by_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_disease_locations_by_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_disease_locations_by_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_disease_locations_by_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