Low Risk

memory_search

Semantic search over the persistent memory store. Returns facts, pack chunks, and past optimizations ranked by vector similarity to the query. Useful for inspecting what ClarifyPrompt would retrieve for a given prompt, and for debugging curator decisions.

Part of the Clarifyprompt server.

memory_search is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE CLARIFYPROMPT →

Free to start. No card required.

AI agents call memory_search to retrieve information from Clarifyprompt without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though memory_search only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

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

See the full Clarifyprompt policy for all 28 tools.

Get this rule live on your own Clarifyprompt server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY CLARIFYPROMPT →

View all 28 tools →

These attack patterns abuse exactly the kind of access memory_search gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so memory_search only ever does what you allow.

SECURE CLARIFYPROMPT →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the memory_search tool do? +

Semantic search over the persistent memory store. Returns facts, pack chunks, and past optimizations ranked by vector similarity to the query. Useful for inspecting what ClarifyPrompt would retrieve for a given prompt, and for debugging curator decisions.. It is categorised as a Read tool in the Clarifyprompt MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on memory_search? +

Register the Clarifyprompt MCP server in PolicyLayer and add a rule for memory_search: 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 Clarifyprompt. Nothing to install.

What risk level is memory_search? +

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

Can I rate-limit memory_search? +

Yes. Add a rate_limit block to the memory_search 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 memory_search completely? +

Set action: deny in the PolicyLayer policy for memory_search. 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 memory_search? +

memory_search is provided by the Clarifyprompt MCP server (clarifyprompt-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Clarifyprompt tool call.

Deterministic rules across all 28 Clarifyprompt tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.