Rerank a list of documents by relevance to a query using Jina Reranker API. Use this when you have multiple documents and want to sort them by how well they match a specific query or topic. Perfect for document retrieval, content filtering, or finding the most relevant information from a collection.
AI agents call sort_by_relevance to retrieve information from Jina AI Remote MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure data retrieval and analysis function. It takes existing documents and metadata (relevance scores) and reorders them. No data is created, modified, deleted, or executed. The only side effect is informational: returning a reordered list. Even if an agent misuses it by reranking irrelevant documents, no harm results from the reranking itself.
From the tool's definition Tool reranks/sorts existing documents by relevance—'sort them by how well they match a specific query'—with no creation, modification, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access sort_by_relevance gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Jina AI Remote MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for sort_by_relevance:
{
"version": "1",
"default": "deny",
"tools": {
"sort_by_relevance": {}
}
} sort_by_relevance 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.
Rerank a list of documents by relevance to a query using Jina Reranker API. Use this when you have multiple documents and want to sort them by how well they match a specific query or topic. Perfect for document retrieval, content filtering, or finding the most relevant information from a collection. It is categorised as a Read tool in the Jina AI Remote MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Jina AI Remote MCP Server MCP server in PolicyLayer and add a rule for sort_by_relevance: 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 Jina AI Remote MCP Server. Nothing to install.
sort_by_relevance 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 sort_by_relevance 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 sort_by_relevance. 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.
sort_by_relevance is provided by the Jina AI Remote MCP Server MCP server (jina-ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Jina AI Remote MCP Server, 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.
21 Jina AI Remote MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.