AI agents call lexq_history_list to retrieve information from LexQ without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays audit/history information about past policy executions. It is a passive query operation that reads existing data without creating, modifying, deleting, executing code, or committing financial transactions. The low severity reflects minimal blast radius—an AI agent misusing this tool would only expose historical metadata about policy runs, not affect live systems or data.
From the tool's definition Tool name 'lexq_history_list' and description 'List policy execution history. Shows trace ID, group, version, status, match result, and latency' indicates retrieval and display of historical data with no modification or side effects.
Attacks that exploit this kind of access
List policy execution history. Shows trace ID, group, version, status, match result, and latency. It is categorised as a Read tool in the LexQ MCP Server, which means it retrieves data without modifying state.
Register the LexQ MCP server in PolicyLayer and add a rule for lexq_history_list: 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 LexQ. Nothing to install.
lexq_history_list 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 lexq_history_list 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 lexq_history_list. 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.
lexq_history_list is provided by the LexQ MCP server (lexq-io/lexq-cli). 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 →