Benefits with Ory + Slack MCP Server
Use Cases
— 01 use caseAgent IAM
Summarizers read at Read, posting agents get Write, Admin adds nothing beyond that today, and Block keeps agents that should never see Slack away.
Core Functionality
— 04 capabilitiesRead, write, admin, or no access
Ory Agent Security classifies every tool on the Slack MCP server as read, write, or admin, so you can give each user, team, or agent type only the level it needs: read for assistants that search conversations, write for agents allowed to post as their user, and no access for agents that shouldn't see internal conversations.
Enforced before execution
Ory Agent Security checks each tool call against the user, the agent acting for them, and any sub-agent inside the agent harness, so a denied message stops before it reaches Slack, with nothing to roll back and no gateway to deploy.
Observe, then enforce
Observe mode shows which agents post and in whose name without blocking anything, so you can apply Ory's pre-built policy for the Slack MCP server and enforce it on your own schedule.
Complete audit trail
Every allow and deny decision on the Slack MCP server streams to your SIEM through OpenTelemetry with the user, agent, and action attached, so you can show which agent sent a message under a user's name.