conversations_request_shared_invite_list

A read tool on the Slack MCP server.

SERVERSlack SOURCEkarbassi/slack-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/karbassi-slack-mcp/conversations-request-shared-invite-list.md

WHAT IT DOES

What conversations_request_shared_invite_list does on Slack

AI agents call conversations_request_shared_invite_list to retrieve information from Slack without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why conversations_request_shared_invite_list is rated Low

The tool name 'conversations_request_shared_invite_list' suggests it lists shared channel invite requests, which is a read operation. The 'list' suffix is a strong indicator of a read/query action. However, the empty description lowers confidence. Severity is low as listing invite requests has minimal blast radius.

From the tool's definition Tool name contains 'list' suggesting a retrieval operation; description is empty providing no additional context

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs conversations_request_shared_invite_list 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_list, this is the rule to start with:

conversations_request_shared_invite_list Allowed

conversations_request_shared_invite_list is read-only, so it stays allowed. 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_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Slack, apply this rule, and every conversations_request_shared_invite_list call is checked against it from then on.

FAQ

Questions about conversations_request_shared_invite_list

What does the conversations_request_shared_invite_list tool do? +

conversations_request_shared_invite_list is a read tool on the Slack MCP server. It is categorised as a Read tool in the Slack MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on conversations_request_shared_invite_list? +

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

conversations_request_shared_invite_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit conversations_request_shared_invite_list? +

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

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

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

KEEP EXPLORING

More on Slack, and thousands of servers like it.

This server

All 233 Slack tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →