Low Risk

get_search_stats

검색 시스템의 성능 통계, 인덱스 상태를 조회합니다.

How to control get_search_stats ↓

What get_search_stats does on Work Memory MCP Server

AI agents call get_search_stats to retrieve information from Work Memory MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_search_stats needs a policy

This tool queries and returns performance metrics and index status information about the search system. It is a read-only operation that retrieves existing data without creating, modifying, deleting, or executing any operations. The blast radius is minimal—misuse would at worst return unwanted statistics but cause no damage to data or system state.

From the tool's definition Tool name 'get_search_stats' and description '검색 시스템의 성능 통계, 인덱스 상태를 조회합니다' (retrieves search system performance statistics and index status) indicate a query/retrieval operation with no data modification or side effects.

Documented attack patterns abuse exactly the kind of access get_search_stats gives an agent:

How to control get_search_stats

PolicyLayer is an MCP gateway — it sits between your AI agents and Work Memory MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_search_stats:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_search_stats": {}
  }
}

get_search_stats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Work Memory MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_search_stats

What does the get_search_stats tool do? +

검색 시스템의 성능 통계, 인덱스 상태를 조회합니다. It is categorised as a Read tool in the Work Memory MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_search_stats? +

Register the Work Memory MCP 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 Work Memory MCP Server. Nothing to install.

What risk level is get_search_stats? +

get_search_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_search_stats? +

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.

How do I block get_search_stats completely? +

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.

What MCP server provides get_search_stats? +

get_search_stats is provided by the Work Memory MCP Server MCP server (moontmsai/work-memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Work Memory MCP Server tool call.

Start from Work Memory MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

24 Work Memory MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.