Map a unified diff to indexed files/symbols and return affected upstream symbols and suggested tests from Lore
AI agents call repo.detect_changes to retrieve information from Lore Context without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
repo.detect_changes analyzes and maps changes to provide traceability information (affected upstream symbols, suggested tests). It performs read-only analysis of indexed data structures without side effects. The tool inspects existing diffs and returns derived information, consistent with Read category behavior like search and fetch operations.
From the tool's definition Tool description: 'Map a unified diff to indexed files/symbols and return affected upstream symbols and suggested tests from Lore' — this is a query/analysis operation that reads diff data and returns information about affected symbols and test suggestions.
Attacks that exploit this kind of access
Map a unified diff to indexed files/symbols and return affected upstream symbols and suggested tests from Lore. It is categorised as a Read tool in the Lore Context MCP Server, which means it retrieves data without modifying state.
Register the Lore Context MCP server in PolicyLayer and add a rule for repo.detect_changes: 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 Lore Context. Nothing to install.
repo.detect_changes 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 repo.detect_changes 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 repo.detect_changes. 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.
repo.detect_changes is provided by the Lore Context MCP server (Lore-Context/lore-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 →