New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

jina_search

Run the jina DeepSearch engine with a given query, retrieving and filtering results.

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

What jina_search does on OrigeneMCP

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

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.

Questions about jina_search

What does the jina_search tool do? +

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.

How do I enforce a policy on jina_search? +

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.

What risk level is jina_search? +

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

Can I rate-limit jina_search? +

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.

How do I block jina_search completely? +

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.

What MCP server provides jina_search? +

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.

More on Origene, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Origene's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.