AI agents use views_push 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.
This tool creates or modifies UI state in Slack by pushing a view onto a stack. While reversible (views can be popped or dismissed), it modifies application state and could be misused to create misleading UI, inject content, or disrupt user experience. It does not delete data (Destructive), execute arbitrary code (Execute), or move money (Financial), making Write the appropriate category.
From the tool's definition Tool name 'views_push' and description 'Push a view onto the stack of a root view' indicates modification of UI state by adding/stacking a view, which is a reversible write operation affecting Slack's interface layer.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Push a view onto the stack of a root view. 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_push: 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_push 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_push 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_push. 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_push 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 →