search_tool_usage
AI agents call search_tool_usage to retrieve information from Mcp Copilotcli History without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description, the server's stated purpose is to enable searching and analyzing stored conversation history without modifying it. The naming pattern and sibling tools all perform retrieval and search operations. This tool likely searches tool usage records within Copilot's local history, making it a Read operation with low severity since it only queries existing data with no side effects.
From the tool's definition Tool name 'search_tool_usage' combined with server context describing 'searching and analyzing GitHub Copilot's conversation history' and sibling tools including 'search_sessions', 'search_by_file_path', and 'get_session_conversation' all indicate data…
Attacks that exploit this kind of access
search_tool_usage. It is categorised as a Read tool in the Mcp Copilotcli History MCP Server, which means it retrieves data without modifying state.
Register the Mcp Copilotcli History MCP server in PolicyLayer and add a rule for search_tool_usage: 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 Mcp Copilotcli History. Nothing to install.
search_tool_usage 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_tool_usage 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_tool_usage. 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_tool_usage is provided by the Mcp Copilotcli History MCP server (micromichaelie/mcp-copilotcli-history). 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 →