get_info_rest
Shows the current version of the Ensembl REST API.
This record as markdown: /tools/gentel-lab-origenemcp/get-info-rest.md
What get_info_rest does on OrigeneMCP
AI agents call get_info_rest 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_info_rest is rated Low
This tool performs a simple informational query to retrieve the API version—a read-only operation with no side effects, no code execution, no data modification, and no irreversible actions. It poses minimal security risk as it only exposes version information.
From the tool's definition Tool name 'get_info_rest' and description 'Shows the current version of the Ensembl REST API' indicate a query operation that retrieves metadata about the API without modifying or executing operations.
Attacks that exploit this kind of access
The rule that runs get_info_rest 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_info_rest, this is the rule to start with:
get_info_rest 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_info_rest call is checked against it from then on.
Questions about get_info_rest
Shows the current version of the Ensembl REST API. 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_info_rest: 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_info_rest 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_info_rest 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_info_rest. 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_info_rest 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