AI agents use workflows_featured_set 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.
The tool name strongly suggests a write operation that modifies which workflows are featured in a Slack workspace. While the description is empty (reducing confidence), the naming convention and server context (full Slack access) indicate this creates or modifies workspace configuration. This is Write rather than Execute because it appears to set a configuration property rather than run arbitrary code.
From the tool's definition Tool name 'workflows_featured_set' suggests setting or modifying featured workflows in Slack. The parent server provides 'full access to Slack' including channels, messages, and workflows.
Attacks that exploit this kind of access
workflows_featured_set. 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.
Register the Slack MCP server in PolicyLayer and add a rule for workflows_featured_set: 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.
workflows_featured_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the workflows_featured_set 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.
Set action: deny in the PolicyLayer policy for workflows_featured_set. 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.
workflows_featured_set 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.
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 →