lexq_rules_update · LexQ MCP: Risk & Policy

WHAT IT DOES

What lexq_rules_update does on LexQ

AI agents use lexq_rules_update to create or update resources in LexQ — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LexQ environment.

WHY IT NEEDS A POLICY

Why lexq_rules_update needs a policy

This tool modifies business rules within a draft state, which is a reversible write operation. The modification of business rules could have significant downstream effects on policy enforcement and automated decisions, justifying high severity, but the reversible nature and draft-only scope (not live production) prevent a higher classification.

From the tool's definition Tool name 'lexq_rules_update' and description 'Update an existing rule in a DRAFT version. Only provided fields are changed.' indicates modification of existing data (rules) in a reversible manner.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lexq_rules_update Rate-limited

lexq_rules_update stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "lexq_rules_update": {
      "limits": [
        {
          "counter": "lexq_rules_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches LexQ, so you can run agents against it safely.

FAQ

Questions about lexq_rules_update

What does the lexq_rules_update tool do? +

Update an existing rule in a DRAFT version. Only provided fields are changed. It is categorised as a Write tool in the LexQ MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on lexq_rules_update? +

Register the LexQ MCP server in PolicyLayer and add a rule for lexq_rules_update: 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.

What risk level is lexq_rules_update? +

lexq_rules_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit lexq_rules_update? +

Yes. Add a rate_limit block to the lexq_rules_update 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.

How do I block lexq_rules_update completely? +

Set action: deny in the PolicyLayer policy for lexq_rules_update. 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.

What MCP server provides lexq_rules_update? +

lexq_rules_update 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.