Low Risk

get_info_assembly

get_info_assembly

How to control get_info_assembly ↓

What get_info_assembly does on OrigeneMCP

AI agents call get_info_assembly 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_assembly needs a policy

The tool name follows a retrieval pattern ('get_info_*') consistent with other read-only tools on the server (check_*, clinvar_query_*, depmap_get_*). Without a description, confidence is moderate, but the semantic suggests fetching or retrieving assembly metadata rather than modifying, executing, or deleting data. Typical use would be accessing reference genome assembly information for research purposes.

From the tool's definition Tool name 'get_info_assembly' suggests retrieval of assembly information. No description provided, but the naming pattern and context (600+ biomedical tools for information retrieval) indicates a query/lookup function.

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

How to control get_info_assembly

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

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

get_info_assembly 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_assembly

What does the get_info_assembly tool do? +

get_info_assembly. 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_assembly? +

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

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

Can I rate-limit get_info_assembly? +

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

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

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