Scan project structure and create a DNA profile (stack, languages, frameworks, patterns). Auto-indexes the result.
AI agents call lctx_scan 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 reads project metadata (files, structure, stack information) and generates a profile/index. While it creates an index as a side effect, that is a non-reversible artifact of analysis rather than modification of the underlying project. The primary action is discovery and profiling of existing project state, making it a Read operation.
From the tool's definition Tool performs scanning and indexing of project structure to create a profile; description uses words like 'scan', 'create a DNA profile', and 'auto-indexes' which indicate information retrieval and analysis with no modification of source data.
Attacks that exploit this kind of access
Scan project structure and create a DNA profile (stack, languages, frameworks, patterns). Auto-indexes the result. 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_scan: 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_scan 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_scan 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_scan. 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_scan 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 →