run_slx · RunWhen Platform MCP: Risk & Policy

WHAT IT DOES

What run_slx does on RunWhen Platform MCP

AI agents invoke run_slx to trigger actions in RunWhen Platform MCP. 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 run_slx needs a policy

SLX execution typically triggers automated workflows, checks, or remediation actions whose effects depend on SLX configuration and arguments. This is an Execute action because it runs configured operations whose consequences are determined at invocation time, not a Read (retrieves data), Write (modifies reversibly), or Destructive (irreversible deletion).

From the tool's definition Tool name 'run_slx' indicates execution of SLX objects (likely RunWhen's service-level execution units). The server description mentions 'run sessions' and 'direct data access to workspaces', suggesting this tool triggers external operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_slx Rate-limited

run_slx 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": {
    "run_slx": {
      "limits": [
        {
          "counter": "run_slx_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 RunWhen Platform MCP, so you can run agents against it safely.

FAQ

Questions about run_slx

What does the run_slx tool do? +

run_slx. It is categorised as a Execute tool in the RunWhen Platform MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_slx? +

Register the RunWhen Platform MCP server in PolicyLayer and add a rule for run_slx: 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 RunWhen Platform MCP. Nothing to install.

What risk level is run_slx? +

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

Can I rate-limit run_slx? +

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

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

run_slx is provided by the RunWhen Platform MCP server (runwhen-contrib/runwhen-platform-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.