Search across dictionary, issues, snippets, research, and progress. Supports keyword (FTS5), semantic (vector), and hybrid (RRF fusion) modes. Returns ranked results with source table, id, and matched snippet.
AI agents call cortex_search to retrieve information from Cortex MCP 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 without creating, modifying, deleting, or executing anything. It supports multiple search modes (keyword, semantic, hybrid) but all are read-only retrieval operations. The blast radius of misuse is minimal—an agent could retrieve unwanted information but cannot alter state or trigger external operations.
From the tool's definition Tool performs search operations across stored data (dictionary, issues, snippets, research, progress) and returns ranked results with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Search across dictionary, issues, snippets, research, and progress. Supports keyword (FTS5), semantic (vector), and hybrid (RRF fusion) modes. Returns ranked results with source table, id, and matched snippet. It is categorised as a Read tool in the Cortex MCP MCP Server, which means it retrieves data without modifying state.
Register the Cortex MCP server in PolicyLayer and add a rule for cortex_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 MCP. Nothing to install.
cortex_search 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 cortex_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.
Set action: deny in the PolicyLayer policy for cortex_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.
cortex_search is provided by the Cortex MCP server (neuralnexustech/cortex-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →