Index git status: branch, diff, recent commits, modified files. AI starts knowing what changed.
AI agents call lctx_git 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 performs query and retrieval operations on git metadata (status, diffs, commit history, file lists). No modifications, deletions, code execution, or side effects are triggered. The 'Index' operation is informational indexing for semantic search/retrieval, not destructive. Confidence is high because the description clearly enumerates read-only git operations.
From the tool's definition Tool description states it 'Index[es] git status: branch, diff, recent commits, modified files' — all read-only operations that retrieve and display git metadata without modifying repositories or files.
Attacks that exploit this kind of access
Index git status: branch, diff, recent commits, modified files. AI starts knowing what changed. 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_git: 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_git 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_git 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_git. 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_git 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 →