AI agents call lexq_rules_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.
The tool retrieves existing rule information from a specific version without creating, modifying, deleting, or executing any business logic. The response is a summary listing of rules, making this a straightforward data retrieval operation with no side effects. Low severity because listing rules poses minimal risk—it exposes schema/configuration information but does not enable harmful actions.
From the tool's definition Tool name and description indicate it 'List all rules in a version' and 'Returns summary with conditionSummary and actionSummary'. This is a read-only operation that retrieves and displays data without modification.
Attacks that exploit this kind of access
List all rules in a version (priority ASC). Returns summary with conditionSummary and actionSummary. 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_rules_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_rules_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_rules_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_rules_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_rules_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 →