get_genome_revision_history

THE RISK

Low Risk

Why get_genome_revision_history needs a policy

This tool retrieves historical information about genome assemblies without modifying, deleting, or executing operations. It is a straightforward read operation that queries biomedical database metadata. There are no side effects, no irreversible actions, and no execution of arbitrary code.

From the tool's definition Tool name 'get_genome_revision_history' and description 'Get revision history for assembly by accession' indicate retrieval of historical metadata about genome assemblies.

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

POLICY

How to control get_genome_revision_history

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

policy.json

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

get_genome_revision_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register OrigeneMCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More OrigeneMCP tools

Execute post_vep_hgvs post_vep_hgvs Execute post_vep_id post_vep_id Write post_archive_id post_archive_id Write post_sequence_id post_sequence_id Write post_variant_recoder post_variant_recoder Write post_variation post_variation Read check_genome_accessions Check the validity of genome accessions Read check_virus_accessions Check virus accessions validity

All 439 OrigeneMCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

Roll out MCP under one policy → Per-person scoped tokens, one central policy, and full audit across every server your team connects.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →
PolicyLayer vs alternatives → How deterministic, per-call MCP policy compares with gateways, identity layers, and authorisation platforms.

FAQ

Questions about get_genome_revision_history

What does the get_genome_revision_history tool do? +

Get revision history for assembly by accession. 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_genome_revision_history? +

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

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

Can I rate-limit get_genome_revision_history? +

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

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

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

CHECK YOUR STACK →