Low Risk

get_disease_efo_id

Get disease EFO ID by disease name.

How to control get_disease_efo_id ↓

What get_disease_efo_id does on OrigeneMCP

AI agents call get_disease_efo_id to retrieve information from OrigeneMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_disease_efo_id needs a policy

This is a straightforward data retrieval tool with no side effects. It performs a read-only query operation to map a disease name to its standardized ontology identifier. There is no data modification, code execution, deletion, or financial impact. The low severity reflects minimal risk even if an AI agent misuses it—worst case it returns incorrect or no results.

From the tool's definition Tool name 'get_disease_efo_id' and description 'Get disease EFO ID by disease name' indicate a lookup/retrieval operation that queries a biomedical database (EFO - Experimental Factor Ontology) to retrieve an identifier based on disease name input.

Documented attack patterns abuse exactly the kind of access get_disease_efo_id gives an agent:

How to control get_disease_efo_id

PolicyLayer is an MCP gateway — it sits between your AI agents and OrigeneMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_disease_efo_id:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_disease_efo_id": {}
  }
}

get_disease_efo_id is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register OrigeneMCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_disease_efo_id

What does the get_disease_efo_id tool do? +

Get disease EFO ID by disease name. It is categorised as a Read tool in the OrigeneMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_disease_efo_id? +

Register the Origene MCP server in PolicyLayer and add a rule for get_disease_efo_id: 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.

What risk level is get_disease_efo_id? +

get_disease_efo_id is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_disease_efo_id? +

Yes. Add a rate_limit block to the get_disease_efo_id 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.

How do I block get_disease_efo_id completely? +

Set action: deny in the PolicyLayer policy for get_disease_efo_id. 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.

What MCP server provides get_disease_efo_id? +

get_disease_efo_id 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.

Enforce policy on every OrigeneMCP tool call.

Start from OrigeneMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

439 OrigeneMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.