analytics_list_zero_result_searches
List recent public search queries that returned zero results. The single best input for
This record as markdown: /tools/com-getmunin-munin/analytics-list-zero-result-searches.md
What analytics_list_zero_result_searches does on Munin
AI agents call analytics_list_zero_result_searches to retrieve information from Munin without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why analytics_list_zero_result_searches is rated Low
This tool retrieves and queries analytics data about zero-result searches. It performs no side effects, creates no data, executes no external operations, and does not delete or modify anything. The action is passive inspection of existing analytics records. The incomplete description ('The single best input for' cuts off) does not suggest any dangerous capability.
From the tool's definition Tool name contains 'list' and description states 'List recent public search queries' — a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
The rule that runs analytics_list_zero_result_searches safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Munin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For analytics_list_zero_result_searches, this is the rule to start with:
analytics_list_zero_result_searches is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Munin, apply this rule, and every analytics_list_zero_result_searches call is checked against it from then on.
Questions about analytics_list_zero_result_searches
List recent public search queries that returned zero results. The single best input for. It is categorised as a Read tool in the Munin MCP Server, which means it retrieves data without modifying state.
Register the Munin MCP server in PolicyLayer and add a rule for analytics_list_zero_result_searches: 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 Munin. Nothing to install.
analytics_list_zero_result_searches 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 analytics_list_zero_result_searches 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 analytics_list_zero_result_searches. 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.
analytics_list_zero_result_searches is provided by the Munin MCP server (https://mcp.getmunin.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Munin, and thousands of servers like it.
This server
Across the catalogue