AI agents call evaluate_retrieval as a supporting operation in Knowledge Rag workflows.
With no description available, I can only infer from the tool name. 'evaluate_retrieval' suggests assessing or scoring retrieval quality, which would be a read/analytical operation. However, given the empty description, confidence is very low.
From the tool's definition Tool name is 'evaluate_retrieval' but description is empty or uninformative.
Documented attack patterns abuse exactly the kind of access evaluate_retrieval gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Knowledge Rag, and nothing reaches the server without passing your rules. This is the rule we recommend for evaluate_retrieval:
{
"version": "1",
"default": "deny",
"tools": {
"evaluate_retrieval": {
"limits": [
{
"counter": "evaluate_retrieval_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
} evaluate_retrieval gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
evaluate_retrieval. It is categorised as a Other tool in the Knowledge Rag MCP Server, which means it performs auxiliary operations.
Register the Knowledge Rag MCP server in PolicyLayer and add a rule for evaluate_retrieval: 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 Knowledge Rag. Nothing to install.
evaluate_retrieval is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the evaluate_retrieval 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 evaluate_retrieval. 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.
evaluate_retrieval is provided by the Knowledge Rag MCP server (lyonzin/knowledge-rag). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Knowledge Rag, 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.
12 Knowledge Rag tools catalogued and risk-classified — across an index of 43,000+ MCP servers.