hybrid_search_memories

Fuse lexical and semantic retrieval with recency using a deterministic RRF ranker.

SERVERMapi Agent Memory SOURCEcabo0m/mapi-agent-memory

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mapi-agent-memory/hybrid-search-memories.md

WHAT IT DOES

What hybrid_search_memories does on Mapi Agent Memory

AI agents call hybrid_search_memories to retrieve information from Mapi Agent Memory without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why hybrid_search_memories is rated Low

Even though hybrid_search_memories only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hybrid_search_memories safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mapi Agent Memory, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hybrid_search_memories, this is the rule to start with:

hybrid_search_memories Allowed

hybrid_search_memories is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hybrid_search_memories": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mapi Agent Memory, apply this rule, and every hybrid_search_memories call is checked against it from then on.

FAQ

Questions about hybrid_search_memories

What does the hybrid_search_memories tool do? +

Fuse lexical and semantic retrieval with recency using a deterministic RRF ranker. It is categorised as a Read tool in the Mapi Agent Memory MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on hybrid_search_memories? +

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

What risk level is hybrid_search_memories? +

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

Can I rate-limit hybrid_search_memories? +

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

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

hybrid_search_memories is provided by the Mapi Agent Memory MCP server (cabo0m/mapi-agent-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mapi Agent Memory, and thousands of servers like it.

This server

All 283 Mapi Agent Memory tools →

Across the catalogue

binary_search on 010 Editor →evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →