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 tool performs ranking and sorting operations on existing documents to present them in order of relevance. It retrieves and reorganizes data but does not create, modify, delete, or execute any external operations. The output is purely informational, making it a Read-category tool with minimal security risk.
From the tool's definition Tool 'reranks' and 'sorts' documents by relevance without modifying, deleting, or executing any data. The description states it is used for 'document retrieval, content filtering, or finding the most relevant information' — all read-only operations.
Attacks that exploit this kind of access
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 (zhijiew/jina-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →