conversations_request_shared_invite_approve

conversations_request_shared_invite_approve

Server Slack karbassi/slack-mcp
Category Write
Risk class Medium
Parameters 00 required

What conversations_request_shared_invite_approve does on Slack

AI agents use conversations_request_shared_invite_approve 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_approve needs a policy

This tool likely creates or modifies channel access permissions by approving a shared invite request. While the empty description reduces certainty, the name clearly indicates a state-change action (approval) rather than retrieval. It is Write rather than Execute because it approves a specific request (reversible) rather than running arbitrary code.

From the tool's definition Tool name contains 'approve' indicating approval of a shared invite request; server provides 'full access to Slack' including channels, and approving invites creates or modifies access permissions and channel membership.

Questions about conversations_request_shared_invite_approve

What does the conversations_request_shared_invite_approve tool do? +

conversations_request_shared_invite_approve. 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_approve? +

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

conversations_request_shared_invite_approve 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_approve? +

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

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

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

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.