conversations_accept_shared_invite

WHAT IT DOES

What conversations_accept_shared_invite does on Slack

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

WHY IT NEEDS A POLICY

Why conversations_accept_shared_invite needs a policy

Accepting a shared invite creates or modifies access permissions and channel membership—a reversible write operation. While not destructive (can be reversed by leaving the channel), it changes organizational state and could grant unintended access to sensitive channels.

From the tool's definition Tool name 'conversations_accept_shared_invite' indicates acceptance of a shared channel invitation, which modifies workspace membership and channel access state. Part of Slack MCP server providing full access to channels and related operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

conversations_accept_shared_invite Rate-limited

conversations_accept_shared_invite 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": {
    "conversations_accept_shared_invite": {
      "limits": [
        {
          "counter": "conversations_accept_shared_invite_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, so you can run agents against it safely.

FAQ

Questions about conversations_accept_shared_invite

What does the conversations_accept_shared_invite tool do? +

conversations_accept_shared_invite. 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 conversations_accept_shared_invite? +

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

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

Can I rate-limit conversations_accept_shared_invite? +

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

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

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