This record as markdown: /tools/gentel-lab-origenemcp/get-lookup-id.md
What get_lookup_id does on OrigeneMCP
AI agents call get_lookup_id 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_lookup_id is rated Low
The name 'get_lookup_id' indicates a retrieval operation that obtains an identifier, typical of Read category tools that query or retrieve data without side effects. Despite the empty description lowering confidence, the 'get' prefix and sibling tools (clinvar_get_*, depmap_get_*) on this biomedical research server are consistently read-only retrievals.
From the tool's definition Tool name 'get_lookup_id' suggests retrieval of an identifier, consistent with Read operations like 'get' and 'fetch'. Description is empty, limiting direct confirmation.
Attacks that exploit this kind of access
The rule that runs get_lookup_id 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_lookup_id, this is the rule to start with:
get_lookup_id is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect OrigeneMCP, apply this rule, and every get_lookup_id call is checked against it from then on.
Questions about get_lookup_id
get_lookup_id 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.
Register the Origene MCP server in PolicyLayer and add a rule for get_lookup_id: 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.
get_lookup_id is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_lookup_id 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.
Set action: deny in the PolicyLayer policy for get_lookup_id. 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.
get_lookup_id 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.
This server
Across the catalogue