Diagnose the Logica Context installation and check dependencies.
AI agents call lctx_doctor 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_doctor retrieves system information about the Logica Context installation and validates its configuration. No data is created, modified, deleted, or executed. The tool is purely informational, making it a Read category risk with low severity, as misuse would only reveal diagnostic data rather than cause operational harm.
From the tool's definition Tool performs diagnostic checks on installation and dependencies — examining existing state without modifying or executing code. Keywords: 'diagnose', 'check' indicate read-only inspection activities.
Attacks that exploit this kind of access
Diagnose the Logica Context installation and check dependencies. 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_doctor: 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_doctor 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_doctor 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_doctor. 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_doctor 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 →