Semantic search using embeddings (Voyage AI or OpenAI). Finds content by meaning, not just keywords. Requires VOYAGE_API_KEY or OPENAI_API_KEY.
AI agents call lctx_semantic 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.
This tool only queries and retrieves data based on semantic similarity. It does not create, modify, delete, or execute any operations. The requirement for API keys is a credential dependency, not a capability that elevates risk. Search/retrieval operations with no side effects are classified as Read with low severity since misuse would only expose existing information, not alter systems or data.
From the tool's definition Tool performs 'semantic search using embeddings' to 'find content by meaning' – a retrieval operation with no data modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Semantic search using embeddings (Voyage AI or OpenAI). Finds content by meaning, not just keywords. Requires VOYAGE_API_KEY or OPENAI_API_KEY. 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_semantic: 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_semantic 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_semantic 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_semantic. 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_semantic 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 →