Low Risk

get_info_external_dbs

get_info_external_dbs

How to control get_info_external_dbs ↓

What get_info_external_dbs does on OrigeneMCP

AI agents call get_info_external_dbs 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_external_dbs needs a policy

The tool name strongly suggests data retrieval ('get_info') from external databases ('external_dbs'), with no indication of modification, deletion, code execution, or financial operations. This aligns with the Read category. Confidence is moderate (0.6) rather than high because the description is uninformative and the specific scope of what 'external_dbs' encompasses is unclear.

From the tool's definition Tool name 'get_info_external_dbs' indicates retrieval of information from external databases. The 'get_info_*' naming pattern and context within a biomedical research platform suggests querying/fetching data. Description is empty, limiting certainty.

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

How to control get_info_external_dbs

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

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

get_info_external_dbs 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_external_dbs

What does the get_info_external_dbs tool do? +

get_info_external_dbs. 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_external_dbs? +

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

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

Can I rate-limit get_info_external_dbs? +

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

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

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