Index text content into the knowledge base for later search. Chunks large content automatically.
AI agents use lctx_index to create or update resources in Logica Context — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Logica Context environment.
The tool writes/stores content into a knowledge base, creating new indexed entries. This is a reversible write operation (data can presumably be removed or updated). It does not execute code, delete data, or involve financial transactions. Severity is medium because an AI agent could inject incorrect or malicious information into a shared team knowledge base, potentially polluting the context used by other sessions.
From the tool's definition Index text content into the knowledge base for later search. Chunks large content automatically.
Attacks that exploit this kind of access
Index text content into the knowledge base for later search. Chunks large content automatically. It is categorised as a Write tool in the Logica Context MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Logica Context MCP server in PolicyLayer and add a rule for lctx_index: 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_index is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the lctx_index 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_index. 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_index 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 →