gateway_run · Slack Max API MCP: Risk & Policy

WHAT IT DOES

What gateway_run does on Slack Max API MCP

AI agents invoke gateway_run to trigger actions in Slack Max API 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 gateway_run needs a policy

This tool executes code-equivalent operations (API method calls and HTTP requests) whose side effects are determined by caller-supplied arguments. While it does not inherently delete data or move money, it can trigger any Slack action or external HTTP operation, making it Execute-category.

From the tool's definition Tool name 'gateway_run' combined with description 'Run a Slack action' and 'Slack Web API method call and generic HTTP call' indicates execution of external operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gateway_run Rate-limited

gateway_run 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": {
    "gateway_run": {
      "limits": [
        {
          "counter": "gateway_run_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 Slack Max API MCP, so you can run agents against it safely.

FAQ

Questions about gateway_run

What does the gateway_run tool do? +

Run a Slack action through a single gateway tool. Supports Slack Web API method call and generic HTTP call. It is categorised as a Execute tool in the Slack Max API 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 gateway_run? +

Register the Slack Max API MCP server in PolicyLayer and add a rule for gateway_run: 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 Slack Max API MCP. Nothing to install.

What risk level is gateway_run? +

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

Can I rate-limit gateway_run? +

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

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

gateway_run is provided by the Slack Max API MCP server (jeongwoobin335/slack-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.