ops_incident_close · Slack Max API MCP: Risk & Policy

WHAT IT DOES

What ops_incident_close does on Slack Max API MCP

AI agents use ops_incident_close 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_close needs a policy

This tool modifies incident records by changing their status and storing final resolution information. These are Write operations — the incident state can theoretically be reopened or modified further. It is not Destructive (no deletion), not Execute (no arbitrary code/command execution), and not Financial.

From the tool's definition Tool description states 'Close a tracked incident, optionally post a closure update, and persist the final resolution' — closing an incident modifies state (marks as closed) and persists data changes (resolution).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ops_incident_close Rate-limited

ops_incident_close 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_close": {
      "limits": [
        {
          "counter": "ops_incident_close_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_close

What does the ops_incident_close tool do? +

Close a tracked incident, optionally post a closure update, and persist the final resolution. 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_close? +

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

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

Can I rate-limit ops_incident_close? +

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

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

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