Low Risk

get_description_by_aid

get_description_by_aid

How to control get_description_by_aid ↓

What get_description_by_aid does on OrigeneMCP

AI agents call get_description_by_aid 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_description_by_aid needs a policy

This tool appears to retrieve or query biomedical data (likely descriptions indexed by AID/accession identifier) from one of the 600+ integrated databases. Read operations on informational biomedical databases pose minimal risk—no data is modified, deleted, or executed. Lower confidence (0.7) due to missing description, but category assignment is robust based on naming pattern and server context.

From the tool's definition Tool name 'get_description_by_aid' indicates retrieval of descriptions by identifier (AID); sibling tools on this server (clinvar_query_*, depmap_get_*) are read-only data retrieval functions.

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

How to control get_description_by_aid

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

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

get_description_by_aid 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_description_by_aid

What does the get_description_by_aid tool do? +

get_description_by_aid. 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_description_by_aid? +

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

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

Can I rate-limit get_description_by_aid? +

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

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

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