get_description_by_cid

A read tool on the Origene MCP server.

SERVEROrigeneMCP SOURCEgentel-lab/origenemcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/gentel-lab-origenemcp/get-description-by-cid.md

WHAT IT DOES

What get_description_by_cid does on OrigeneMCP

AI agents call get_description_by_cid 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.

RISK

Why get_description_by_cid is rated Low

The 'get_' prefix and '_by_cid' suffix indicate this retrieves data (likely a chemical compound description from PubChem or similar database using a Compound ID) without side effects. Even with empty description, the functional pattern aligns with querying biomedical reference data.

From the tool's definition Tool name 'get_description_by_cid' suggests a retrieval operation (get_*) that fetches a description by a chemical identifier (cid).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_description_by_cid 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_description_by_cid, this is the rule to start with:

get_description_by_cid Allowed

get_description_by_cid is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_description_by_cid": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect OrigeneMCP, apply this rule, and every get_description_by_cid call is checked against it from then on.

FAQ

Questions about get_description_by_cid

What does the get_description_by_cid tool do? +

get_description_by_cid is a read tool on the Origene MCP server. 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_cid? +

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

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

Can I rate-limit get_description_by_cid? +

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

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

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

KEEP EXPLORING

More on Origene, and thousands of servers like it.

This server

All 439 Origene tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →