Get statistics about stored embeddings and semantic search status
AI agents call get_embedding_stats to retrieve information from Claude Memory Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns statistical information about embeddings and search status. It has no side effects, does not create, modify, delete, or execute operations. It is a read-only query operation with minimal blast radius if misused by an AI agent—at worst, it exposes information about the embedding system's state.
From the tool's definition Tool name 'get_embedding_stats' and description 'Get statistics about stored embeddings and semantic search status' indicate a retrieval operation that queries metadata about embeddings without modifying or deleting data.
Attacks that exploit this kind of access
Get statistics about stored embeddings and semantic search status. It is categorised as a Read tool in the Claude Memory Server MCP Server, which means it retrieves data without modifying state.
Register the Claude Memory Server MCP server in PolicyLayer and add a rule for get_embedding_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 Claude Memory Server. Nothing to install.
get_embedding_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_embedding_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_embedding_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_embedding_stats is provided by the Claude Memory Server MCP server (xiy/claude-memory-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 →