search_target

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/search-target.md

WHAT IT DOES

What search_target does on OrigeneMCP

AI agents call search_target 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 search_target is rated Low

Without a description, confidence is reduced. However, the naming convention ('search_target') and the exclusively read-only nature of all sibling tools strongly suggest this is a query/search tool for biomedical data with no write, execute, or destructive capabilities. The low severity reflects typical read operations on reference databases.

From the tool's definition Tool name 'search_target' suggests information retrieval. The empty description prevents full certainty, but context from sibling tools (clinvar_find_single_mutation, depmap_get_dependency, depmap_get_expression, check_genome_accessions) all perform read-only…

Attacks that exploit this kind of access

RECOMMENDED RULE

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

search_target Allowed

search_target 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": {
    "search_target": {}
  }
}

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 search_target call is checked against it from then on.

FAQ

Questions about search_target

What does the search_target tool do? +

search_target 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 search_target? +

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

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

Can I rate-limit search_target? +

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

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

search_target 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

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

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