Low Risk

get_info_divisions

Get Ensembl divisions.

How to control get_info_divisions ↓

What get_info_divisions does on OrigeneMCP

AI agents call get_info_divisions 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_info_divisions needs a policy

This tool performs a simple informational query to retrieve data about Ensembl divisions—a static reference dataset used in biomedical research. It has no side effects, does not modify data, does not execute arbitrary code, and does not trigger external operations. The blast radius of misuse is negligible since the information returned is public, non-sensitive metadata about database structure.

From the tool's definition Tool name 'get_info_divisions' and description 'Get Ensembl divisions' indicate a retrieval operation that queries metadata about Ensembl database divisions with no modification or execution of code.

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

How to control get_info_divisions

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_info_divisions:

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

get_info_divisions 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_info_divisions

What does the get_info_divisions tool do? +

Get Ensembl divisions. 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_info_divisions? +

Register the Origene MCP server in PolicyLayer and add a rule for get_info_divisions: 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_info_divisions? +

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

Can I rate-limit get_info_divisions? +

Yes. Add a rate_limit block to the get_info_divisions 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_info_divisions completely? +

Set action: deny in the PolicyLayer policy for get_info_divisions. 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_info_divisions? +

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