conversations_request_shared_invite_deny

What conversations_request_shared_invite_deny does on Slack

AI agents use conversations_request_shared_invite_deny 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 conversations_request_shared_invite_deny is rated Medium

This tool writes/modifies data (invite request state) but does not irreversibly delete or destroy data (thus not Destructive). It does not execute arbitrary code or trigger external side effects (thus not Execute). It does not move money (thus not Financial). The action is reversible — a denied invite could theoretically be re-requested or re-sent.

From the tool's definition Tool name contains 'deny' and description states 'Deny a shared channel invite request' — this modifies the state of an invite request by rejecting it, which is a reversible administrative action on Slack's collaboration infrastructure.

The rule that runs conversations_request_shared_invite_deny safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Slack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For conversations_request_shared_invite_deny, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "conversations_request_shared_invite_deny": {
      "limits": [
        {
          "counter": "conversations_request_shared_invite_deny_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about conversations_request_shared_invite_deny