Semantic + keyword + graph traversal search across all node types. Use for broad discovery. Returns a Markdown string.
AI agents call search_context to retrieve information from Memex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data from the knowledge graph without side effects. It enables discovery across nodes and relationships but does not create, modify, delete, or execute any operations. The return of static Markdown output confirms read-only retrieval semantics.
From the tool's definition Tool performs 'Semantic + keyword + graph traversal search' and 'Returns a Markdown string'. The description explicitly describes search/discovery operations with no modification or execution capabilities.
Documented attack patterns abuse exactly the kind of access search_context gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Memex, and nothing reaches the server without passing your rules. This is the rule we recommend for search_context:
{
"version": "1",
"default": "deny",
"tools": {
"search_context": {}
}
}search_context is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Semantic + keyword + graph traversal search across all node types. Use for broad discovery. Returns a Markdown string. It is categorised as a Read tool in the Memex MCP Server, which means it retrieves data without modifying state.
Register the Memex MCP server in PolicyLayer and add a rule for search_context: 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 Memex. Nothing to install.
search_context 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 search_context 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 search_context. 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.
search_context is provided by the Memex MCP server (stifler7/memex). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Memex, 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.
13 Memex tools catalogued and risk-classified — across an index of 43,000+ MCP servers.