New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_description_by_sid

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-sid.md

What get_description_by_sid does on OrigeneMCP

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

Why get_description_by_sid is rated Low

The 'get_' prefix and the context of a biomedical database platform indicate this tool retrieves pre-existing data without modification. However, confidence is moderate (0.7) because the description is empty, preventing confirmation of exact behavior. No mutation, deletion, execution, or financial implications are evident from context.

From the tool's definition Tool name 'get_description_by_sid' suggests retrieval of descriptive information by identifier. Sibling tools (check_genome_accessions, clinvar_find_single_mutation, depmap_get_expression) are all read-only queries.

Questions about get_description_by_sid

What does the get_description_by_sid tool do? +

get_description_by_sid 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_sid? +

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

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

Can I rate-limit get_description_by_sid? +

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

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

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

More on Origene, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Origene's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.