Compose governed, agent-ready context for a user query from memory, web, repo evidence, and tool traces. Use this as the default read path before answering from Lore memory.
AI agents call context_query 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.
The tool retrieves and queries data from multiple sources (memory, web, repo, traces) to assemble context for an agent. The verb 'compose' means to gather/assemble existing information, not to create new data or trigger external operations. No irreversible actions, financial transactions, or code execution are described. This is a straightforward data retrieval operation.
From the tool's definition Tool is described as a 'read path' that 'compose[s]' context by querying 'memory, web, repo evidence, and tool traces' — retrieving and aggregating existing data with no modifications, deletions, or side effects.
Attacks that exploit this kind of access
Compose governed, agent-ready context for a user query from memory, web, repo evidence, and tool traces. Use this as the default read path before answering from Lore memory. 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 context_query: 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.
context_query 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 context_query 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 context_query. 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.
context_query 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 →