conversations_request_shared_invite_deny

WHAT IT DOES

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 IT NEEDS A POLICY

Why conversations_request_shared_invite_deny needs a policy

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.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

conversations_request_shared_invite_deny Rate-limited

conversations_request_shared_invite_deny 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_request_shared_invite_deny": {
      "limits": [
        {
          "counter": "conversations_request_shared_invite_deny_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_request_shared_invite_deny

What does the conversations_request_shared_invite_deny tool do? +

Deny a shared channel invite request. 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_request_shared_invite_deny? +

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

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

Can I rate-limit conversations_request_shared_invite_deny? +

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

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

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