Run the jina DeepSearch engine with a given query, retrieving and filtering results.
AI agents call jina_search 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.
This tool performs information retrieval—running a search query and returning filtered results. It has no side effects, does not modify data, execute code, delete anything, or move money. The verb 'retrieving' and the search-engine context clearly indicate a read-only operation. Confidence is high because the description is explicit about retrieval with filtering, which are characteristic Read operations.
From the tool's definition Tool name is 'jina_search' and description states it 'retrieves and filtering results' from a search engine with no mention of modification, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access jina_search gives an agent:
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 jina_search:
{
"version": "1",
"default": "deny",
"tools": {
"jina_search": {}
}
}jina_search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Run the jina DeepSearch engine with a given query, retrieving and filtering results. 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 jina_search: 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.
jina_search 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 jina_search 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 jina_search. 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.
jina_search 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.
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.