Search the knowledge base using BM25 full-text search with Porter stemming. Supports multiple queries.
AI agents call lctx_search to retrieve information from Logica Context without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
lctx_search retrieves and queries data from a knowledge base without side effects. It matches the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The full-text search with stemming is a standard information retrieval operation that does not create, modify, delete, or execute arbitrary code.
From the tool's definition Tool performs 'full-text search' on a knowledge base with no capability to modify, delete, or execute operations. Description explicitly describes retrieval functionality: 'Search the knowledge base using BM25 full-text search with Porter stemming.
Attacks that exploit this kind of access
Search the knowledge base using BM25 full-text search with Porter stemming. Supports multiple queries. It is categorised as a Read tool in the Logica Context MCP Server, which means it retrieves data without modifying state.
Register the Logica Context MCP server in PolicyLayer and add a rule for lctx_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 Logica Context. Nothing to install.
lctx_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 lctx_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 lctx_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.
lctx_search is provided by the Logica Context MCP server (rovemark/logica-context). 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 →