Post reminder replies to SLA-breached threads across channels (supports dry-run).
AI agents use ops_sla_followup 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.
This tool posts messages (replies) to Slack threads across multiple channels, which is a Write operation. The blast radius is high because it can send messages across many channels simultaneously to SLA-breached threads, potentially spamming numerous conversations. The dry-run support suggests awareness of the broad impact. It does not delete or execute code, so Write is the most appropriate category.
From the tool's definition Post reminder replies to SLA-breached threads across channels (supports dry-run)
Attacks that exploit this kind of access
Post reminder replies to SLA-breached threads across channels (supports dry-run). 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.
Register the Slack Max API MCP server in PolicyLayer and add a rule for ops_sla_followup: 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.
ops_sla_followup is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ops_sla_followup 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.
Set action: deny in the PolicyLayer policy for ops_sla_followup. 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.
ops_sla_followup 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →