Show search usage analytics: query counts, zero-result queries, low-relevance queries, top searched terms.
AI agents call search_analytics to retrieve information from Local Rag without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays analytics data about past search behavior. It performs no data modification, deletion, code execution, or financial operations. The most severe capability is read-only aggregation of usage statistics, which poses minimal risk even if misused by an AI agent—at worst it could leak information about what users have searched for, a low-severity concern.
From the tool's definition Tool description explicitly states it 'Show[s] search usage analytics' with read-only operations: 'query counts, zero-result queries, low-relevance queries, top searched terms.' All operations are retrieval and aggregation of existing metrics with no…
Documented attack patterns abuse exactly the kind of access search_analytics gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Local Rag, and nothing reaches the server without passing your rules. This is the rule we recommend for search_analytics:
{
"version": "1",
"default": "deny",
"tools": {
"search_analytics": {}
}
}search_analytics 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.
Show search usage analytics: query counts, zero-result queries, low-relevance queries, top searched terms. It is categorised as a Read tool in the Local Rag MCP Server, which means it retrieves data without modifying state.
Register the Local Rag MCP server in PolicyLayer and add a rule for search_analytics: 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 Local Rag. Nothing to install.
search_analytics 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 search_analytics 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 search_analytics. 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.
search_analytics is provided by the Local Rag MCP server (thewinci/mimirs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Local 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.
29 Local Rag tools catalogued and risk-classified — across an index of 43,000+ MCP servers.