Low Risk

cortex_knowledge_search

Search the platform knowledge base by semantic similarity. Returns relevant document snippets with metadata, tags, and hit counts. Supports filtering by tags, project, hall type (MemPalace-inspired hierarchy), and

How to control cortex_knowledge_search ↓

What cortex_knowledge_search does on Cortex Hub

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

Low Risk

Why cortex_knowledge_search needs a policy

This is a retrieval operation that queries existing data without side effects. It searches and returns information from a knowledge base with optional filtering parameters. The description explicitly states it 'Returns relevant document snippets' rather than modifying, deleting, or executing any operations. No code execution, financial transactions, or data mutation occurs.

From the tool's definition Tool performs semantic search of knowledge base returning document snippets with metadata, tags, and hit counts. Uses passive query operations (search, filter) with no modification, deletion, or execution capabilities.

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

How to control cortex_knowledge_search

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

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

cortex_knowledge_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 Cortex Hub — 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 cortex_knowledge_search

What does the cortex_knowledge_search tool do? +

Search the platform knowledge base by semantic similarity. Returns relevant document snippets with metadata, tags, and hit counts. Supports filtering by tags, project, hall type (MemPalace-inspired hierarchy), and. It is categorised as a Read tool in the Cortex Hub MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cortex_knowledge_search? +

Register the Cortex Hub MCP server in PolicyLayer and add a rule for cortex_knowledge_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 Cortex Hub. Nothing to install.

What risk level is cortex_knowledge_search? +

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

Can I rate-limit cortex_knowledge_search? +

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

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

cortex_knowledge_search is provided by the Cortex Hub MCP server (lktiep/cortex-hub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Cortex Hub tool call.

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

25 Cortex Hub 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.