LexQ

63 tools. 30 can modify or destroy data without limits.

8 destructive tools with no built-in limits. Policy required.

Last updated:

30 can modify or destroy data
33 read-only
63 tools total

Community server · catalogue entry verified 03/07/2026

How to control LexQ ↓

What LexQ exposes to your agents

Read (33) Write / Execute (22) Destructive / Financial (8)
Critical Risk

The most dangerous LexQ tools

30 of LexQ's 63 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control LexQ

PolicyLayer is an MCP gateway — it sits between your AI agents and LexQ, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations
{
  "lexq_deploy_rollback": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "lexq_domain_templates_apply": {
    "limits": [
      {
        "counter": "lexq_domain_templates_apply_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "lexq_ab_test_adjust": {
    "limits": [
      {
        "counter": "lexq_ab_test_adjust_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register LexQ — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON LEXQ →

Instant setup, no code required.

All 63 LexQ tools

WRITE 15 tools
Write lexq_domain_templates_apply Apply a domain template to the current tenant. Creates the template Write lexq_facts_create Register a new input variable. Key must be lowercase with underscores (e.g. payment_amount). Types: STRING, NU Write lexq_facts_update Update a fact definition. Key and type cannot be changed. Only provided fields are updated. System facts only Write lexq_groups_create Create a new policy group. Requires name. Priority is auto-assigned (appended last, tenant-wide); use lexq_gro Write lexq_groups_reorder Reorder policy groups by priority. Priority is tenant-wide and flat (1...N continuous); array index 0 = priori Write lexq_groups_update Update a policy group. Only provided fields are updated; omitted fields remain unchanged. Write lexq_integrations_save Create or update an integration. Provide id to update an existing one; omit id to create new. Types: COUPON, P Write lexq_logs_bulk_action Process multiple failure logs at once. Provide an array of log IDs and the action. Write lexq_rules_reorder Reorder rules by specifying rule IDs in desired order. Priorities are assigned 1...N (1-based, continuous); ar Write lexq_rules_toggle Enable or disable a rule without deleting it. Write lexq_rules_update Update an existing rule in a DRAFT version. Only provided fields are changed. Write lexq_versions_clone Clone an existing version to create a new DRAFT. Useful when the source version is already published. Write lexq_versions_create Create a new DRAFT version in a policy group. Optionally provide a commit message and effective date range. Write lexq_versions_update Update a DRAFT version. Only DRAFT versions can be modified. Only provided fields are changed. Write lexq_webhook_subscriptions_save Create or update a webhook subscription. Omit id to create, provide id to update. Events: VERSION_PUBLISHED, D
READ 33 tools
Read lexq_ab_test_adjust Adjust traffic rate of a running A/B test. Read lexq_dataset_template Generate a sample CSV or JSON template based on the required facts of a version. Use this to understand the ex Read lexq_deploy_deployable List ACTIVE (published) versions that can be deployed for a group. Use this to find which versions are availab Read lexq_deploy_detail Get detailed info about a specific deployment including snapshot hash and integrity check. Read lexq_deploy_diff Compare rule snapshots between two versions. Shows added, removed, and modified rules. Useful for reviewing ch Read lexq_deploy_history List deployment history across all groups. Read lexq_deploy_overview Show current deployment status of all groups — which version is live, last deployment type, and deployer. Read lexq_domain_templates_list List all domain templates. A domain template is a curated, industry-specific starter pack of fact definitions Read lexq_domain_templates_preview Preview exactly what a domain template will provision before applying it: the fact definitions it registers, t Read lexq_facts_action_metadata Retrieve runtime fact requirements per Action type. For each Action, shows which input facts must be present i Read lexq_facts_list List all fact definitions (input variable schema). Shows key, type, and required status. Always check this bef Read lexq_facts_unregistered List facts referenced by a version Read lexq_groups_get Get a single policy group by ID. Read lexq_groups_list List all policy groups (tenant-wide, priority ASC). Read lexq_history_get Get full execution detail including inputFacts, mutatedFacts, generatedVariables, executionTraces, and decisio Read lexq_history_list List policy execution history. Shows trace ID, group, version, status, match result, and latency. Read lexq_history_stats Get execution KPIs: total executions, success/failure counts, success rate, and average latency. Read lexq_integrations_config_spec Show available integration types and their required configuration fields. Read lexq_integrations_get Get integration detail by ID. Read lexq_integrations_list List all external integrations (webhooks, CRM, notification, etc.). Read lexq_logs_get Get failure log detail by ID. Read lexq_logs_list List system failure logs from background tasks (webhook calls, coupon issuance, etc.). Read lexq_requirements Analyze which input facts a version requires. Returns required keys, types, and an example request body. Read lexq_rules_get Get full rule detail including condition tree and action definitions. Read lexq_rules_list List all rules in a version (priority ASC). Returns summary with conditionSummary and actionSummary. Read lexq_simulation_export Export simulation results as JSON or CSV. Returns the raw data. Read lexq_simulation_list List simulation history with optional filters. Read lexq_simulation_status Get simulation status and results. Poll until status is COMPLETED or FAILED. Read lexq_versions_get Get a single version by ID, including its rules and fact requirements. Read lexq_versions_list List all versions of a policy group. Read lexq_webhook_subscriptions_get Get webhook subscription detail by ID. Read lexq_webhook_subscriptions_list List platform event webhook subscriptions. These receive deployment lifecycle notifications (publish, deploy, Read lexq_whoami Show current authentication info (tenant name, role, API key mask).

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about LexQ

Can an AI agent delete data through the LexQ MCP server? +

Yes. The LexQ server exposes 8 destructive tools including lexq_deploy_rollback, lexq_facts_delete, lexq_groups_delete. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through LexQ? +

The LexQ server has 15 write tools including lexq_domain_templates_apply, lexq_facts_create, lexq_facts_update. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach LexQ.

How many tools does the LexQ MCP server expose? +

63 tools across 4 categories: Destructive, Execute, Read, Write. 33 are read-only. 30 can modify, create, or delete data.

How do I enforce a policy on LexQ? +

Register the LexQ MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every LexQ tool call.

Deterministic rules across all 63 LexQ tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

63 LexQ tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// WHERE THIS COMES FROM

These policies come from LexQ's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.