Medium Risk

SLACK_ARCHIVE_A_SLACK_CONVERSATION

Archives a Slack conversation by its ID, rendering it read-only and hidden while retaining history, ideal for cleaning up inactive channels; be aware that some channels (like #general or certain DMs) cannot be archived and this may impact connected integrations.

Part of the Slack server.

SLACK_ARCHIVE_A_SLACK_CONVERSATION can modify Slack data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE SLACK →

Free to start. No card required.

AI agents use SLACK_ARCHIVE_A_SLACK_CONVERSATION to create or modify resources in Slack. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call SLACK_ARCHIVE_A_SLACK_CONVERSATION repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Slack.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "SLACK_ARCHIVE_A_SLACK_CONVERSATION": {
      "limits": [
        {
          "counter": "slack_archive_a_slack_conversation_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Slack policy for all 143 tools.

Get this rule live on your own Slack server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY SLACK →

View all 143 tools →

These attack patterns abuse exactly the kind of access SLACK_ARCHIVE_A_SLACK_CONVERSATION gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so SLACK_ARCHIVE_A_SLACK_CONVERSATION only ever does what you allow.

SECURE SLACK →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the SLACK_ARCHIVE_A_SLACK_CONVERSATION tool do? +

Archives a Slack conversation by its ID, rendering it read-only and hidden while retaining history, ideal for cleaning up inactive channels; be aware that some channels (like #general or certain DMs) cannot be archived and this may impact connected integrations.. It is categorised as a Write tool in the Slack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on SLACK_ARCHIVE_A_SLACK_CONVERSATION? +

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

What risk level is SLACK_ARCHIVE_A_SLACK_CONVERSATION? +

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

Can I rate-limit SLACK_ARCHIVE_A_SLACK_CONVERSATION? +

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

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

SLACK_ARCHIVE_A_SLACK_CONVERSATION is provided by the Slack MCP server (@modelcontextprotocol/server-slack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Slack tool call.

Deterministic rules across all 143 Slack tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.