This record as markdown: /tools/karbassi-slack-mcp/views-publish.md
What views_publish does on Slack
AI agents use views_publish 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 views_publish is rated Medium
Without an explicit description, classification relies on the tool name and context. 'Publish' indicates a write operation that creates or modifies Slack views/content. This is reversible (views can be updated or unpublished), placing it in Write rather than Destructive. Severity is high because a compromised agent could publish misleading, phishing, or spam content to users' Slack workspaces, affecting many users.
From the tool's definition Tool name 'views_publish' suggests publishing or posting content to Slack views (likely modal dialogs, home tabs, or other UI surfaces).
Attacks that exploit this kind of access
The rule that runs views_publish 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 views_publish, this is the rule to start with:
views_publish 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Slack, apply this rule, and every views_publish call is checked against it from then on.
Questions about views_publish
views_publish is a write tool on the Slack MCP server. 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 views_publish: 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.
views_publish 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 views_publish 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 views_publish. 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.
views_publish 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.
More on Slack, and thousands of servers like it.
This server
Across the catalogue