lexq_webhook_subscriptions_save · LexQ MCP: Risk & Policy

WHAT IT DOES

What lexq_webhook_subscriptions_save does on LexQ

AI agents use lexq_webhook_subscriptions_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_webhook_subscriptions_save needs a policy

This tool creates or modifies webhook subscription configurations, which are reversible data changes. The tool enables configuration of notifications for business-critical events (VERSION_PUBLISHED, DEPLOYED, ROLLED_BACK, UNDEPLOYED).

From the tool's definition Create or update a webhook subscription. Omit id to create, provide id to update.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lexq_webhook_subscriptions_save Rate-limited

lexq_webhook_subscriptions_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_webhook_subscriptions_save": {
      "limits": [
        {
          "counter": "lexq_webhook_subscriptions_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_webhook_subscriptions_save

What does the lexq_webhook_subscriptions_save tool do? +

Create or update a webhook subscription. Omit id to create, provide id to update. Events: VERSION_PUBLISHED, DEPLOYED, ROLLED_BACK, UNDEPLOYED. Formats: GENERIC (full JSON), SLACK ({. 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_webhook_subscriptions_save? +

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

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

Can I rate-limit lexq_webhook_subscriptions_save? +

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

Set action: deny in the PolicyLayer policy for lexq_webhook_subscriptions_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_webhook_subscriptions_save? +

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