Analyze tool search usage patterns. Shows most common queries, low-confidence results, and gaps where users searched but found poor matches. Use this to identify which tools are hard to discover.
AI agents call pilotgentic_search_analytics to retrieve information from PilotGentic without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval and analysis of search patterns and usage metrics. It reads historical data about queries and tool discovery, presents statistics, and identifies gaps—all passive, informational operations with no side effects. No data is created, modified, deleted, or executed; it is purely observational analytics.
From the tool's definition Tool description explicitly states 'Analyze tool search usage patterns' and 'Shows most common queries, low-confidence results, and gaps'. These are read-only analytic operations that retrieve and display usage data without modifying or executing anything.
Attacks that exploit this kind of access
Analyze tool search usage patterns. Shows most common queries, low-confidence results, and gaps where users searched but found poor matches. Use this to identify which tools are hard to discover. It is categorised as a Read tool in the PilotGentic MCP Server, which means it retrieves data without modifying state.
Register the PilotGentic MCP server in PolicyLayer and add a rule for pilotgentic_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 PilotGentic. Nothing to install.
pilotgentic_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 pilotgentic_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 pilotgentic_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.
pilotgentic_search_analytics is provided by the PilotGentic MCP server (@pilotgentic/mcp-server). 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 →