lexq_integrations_save · LexQ MCP: Risk & Policy

WHAT IT DOES

What lexq_integrations_save does on LexQ

AI agents use lexq_integrations_save 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_integrations_save needs a policy

This tool modifies system configurations by creating or updating integrations that connect to external services (CRM, webhooks, notification systems, etc.). While reversible, it carries high severity because misconfigured or malicious integrations could redirect business-critical data flows, trigger unintended notifications, or expose systems to external services.

From the tool's definition Tool description states 'Create or update an integration' with support for types including WEBHOOK, COUPON, POINT, and NOTIFICATION systems. These are reversible data modifications that create or alter integration configurations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lexq_integrations_save Rate-limited

lexq_integrations_save 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_integrations_save": {
      "limits": [
        {
          "counter": "lexq_integrations_save_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_integrations_save

What does the lexq_integrations_save tool do? +

Create or update an integration. Provide id to update an existing one; omit id to create new. Types: COUPON, POINT, NOTIFICATION, CRM, MESSENGER, WEBHOOK. 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_integrations_save? +

Register the LexQ MCP server in PolicyLayer and add a rule for lexq_integrations_save: 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_integrations_save? +

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

Can I rate-limit lexq_integrations_save? +

Yes. Add a rate_limit block to the lexq_integrations_save 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_integrations_save completely? +

Set action: deny in the PolicyLayer policy for lexq_integrations_save. 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_integrations_save? +

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