lexq_deploy_publish · LexQ MCP: Risk & Policy

WHAT IT DOES

What lexq_deploy_publish does on LexQ

AI agents invoke lexq_deploy_publish to trigger actions in LexQ. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why lexq_deploy_publish needs a policy

Publishing a draft to active status triggers an external state transition that locks the version from further edits, making it effectively irreversible without a separate rollback action. This is an operational deployment trigger rather than a simple write, and the locking behavior means it cannot be trivially undone — misuse could push broken business rules into production.

From the tool's definition Publish a DRAFT version (DRAFT → ACTIVE). Locks the version from further edits.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lexq_deploy_publish Rate-limited

lexq_deploy_publish stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_deploy_publish": {
      "limits": [
        {
          "counter": "lexq_deploy_publish_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_deploy_publish

What does the lexq_deploy_publish tool do? +

Publish a DRAFT version (DRAFT → ACTIVE). Locks the version from further edits. Must have at least one rule. Undefined facts referenced by rules do not block publishing (INV-4); call lexq_facts_unregistered first to review them. It is categorised as a Execute tool in the LexQ MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on lexq_deploy_publish? +

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

lexq_deploy_publish is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit lexq_deploy_publish? +

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

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

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