ops_incident_create · Slack Max API MCP: Risk & Policy

WHAT IT DOES

What ops_incident_create does on Slack Max API MCP

AI agents use ops_incident_create to create or update resources in Slack Max API MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Slack Max API MCP environment.

WHY IT NEEDS A POLICY

Why ops_incident_create needs a policy

This tool creates new incident records (reversible data creation) and may trigger notifications/announcements in Slack. While it affects workspace state and communication, the action is not destructive (records can be modified or archived), not financial, and not code execution. It fits the Write category as it modifies data reversibly.

From the tool's definition Tool description states 'Create and optionally announce a tracked incident record' — the verb 'create' indicates data creation. The capability to 'announce' suggests messaging side effects within Slack but no permanent deletion or financial transactions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ops_incident_create Rate-limited

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

FAQ

Questions about ops_incident_create

What does the ops_incident_create tool do? +

Create and optionally announce a tracked incident record using config-backed incident templates. It is categorised as a Write tool in the Slack Max API MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ops_incident_create? +

Register the Slack Max API MCP server in PolicyLayer and add a rule for ops_incident_create: 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 ops_incident_create? +

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

Can I rate-limit ops_incident_create? +

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

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

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