Get statistics about the search index
AI agents call get_search_stats to retrieve information from Memex Targeted Search Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves statistical information about an existing search index. It performs a query operation with no capability to modify, delete, or execute code. The blast radius of misuse is minimal—an agent could only receive factual information about index size, document counts, or similar benign metrics. This is a straightforward Read operation.
From the tool's definition Tool name 'get_search_stats' and description 'Get statistics about the search index' indicate retrieval of statistical metadata without modification. The verb 'Get' and the read-only nature of querying index statistics confirm no side effects.
Attacks that exploit this kind of access
Get statistics about the search index. It is categorised as a Read tool in the Memex Targeted Search Server MCP Server, which means it retrieves data without modifying state.
Register the Memex Targeted Search Server MCP server in PolicyLayer and add a rule for get_search_stats: 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 Memex Targeted Search Server. Nothing to install.
get_search_stats 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 get_search_stats 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 get_search_stats. 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.
get_search_stats is provided by the Memex Targeted Search Server MCP server (memextech/memex-targeted-search-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 →