lexq_logs_action · LexQ MCP: Risk & Policy

WHAT IT DOES

What lexq_logs_action does on LexQ

AI agents invoke lexq_logs_action 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_logs_action needs a policy

The tool triggers re-execution of failed operations or modifies their status. RETRY actively re-executes payloads (Execute category), while RESOLVE and IGNORE modify system state. Since the most severe action is re-executing business rule logic with original payloads, Execute is the appropriate category. Misuse could cause unintended re-processing of business transactions at scale.

From the tool's definition RETRY (re-execute with original payload), RESOLVE (mark as manually fixed), or IGNORE (skip intentionally)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lexq_logs_action Rate-limited

lexq_logs_action 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_logs_action": {
      "limits": [
        {
          "counter": "lexq_logs_action_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_logs_action

What does the lexq_logs_action tool do? +

Process a single failure log: RETRY (re-execute with original payload), RESOLVE (mark as manually fixed), or IGNORE (skip intentionally). 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_logs_action? +

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

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

Can I rate-limit lexq_logs_action? +

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

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

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