Low Risk

memory_contextual_search

Perform contextual memory retrieval with intelligent ranking

How to control memory_contextual_search ↓

What memory_contextual_search does on Documcp

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

Low Risk

Why memory_contextual_search needs a policy

This tool performs information retrieval and ranking of contextual memory—a read-only operation that queries existing data without creating, modifying, deleting, or executing code. It has minimal blast radius as misuse would only surface incorrect or irrelevant search results, not cause structural or financial damage.

From the tool's definition Tool name 'memory_contextual_search' and description 'Perform contextual memory retrieval with intelligent ranking' indicate retrieval/query operations with no modification or execution of external commands.

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

How to control memory_contextual_search

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

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

memory_contextual_search 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 Documcp — 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 memory_contextual_search

What does the memory_contextual_search tool do? +

Perform contextual memory retrieval with intelligent ranking. It is categorised as a Read tool in the Documcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on memory_contextual_search? +

Register the Docu MCP server in PolicyLayer and add a rule for memory_contextual_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 Documcp. Nothing to install.

What risk level is memory_contextual_search? +

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

Can I rate-limit memory_contextual_search? +

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

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

memory_contextual_search is provided by the Docu MCP server (tosin2013/documcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Documcp tool call.

Start from Documcp, 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.

52 Documcp 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.