views_update

What views_update does on Slack

AI agents use views_update 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_update is rated Medium

The 'views_update' tool modifies Slack views—likely modals, home tabs, or canvas content—which are data structures that can be changed but not irreversibly deleted. This is a Write operation. Severity is high because an agent could modify views to phish users, inject misleading content, or disrupt workspace UX at scale across channels or users. The broad access model described ('full access to Slack') amplifies risk.

From the tool's definition Tool name 'views_update' combined with server description stating 'full access to Slack: messages, channels, files, canvases, lists' indicates modification of Slack UI views/canvases. The 'update' operation is reversible (Write category).

The rule that runs views_update 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_update, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "views_update": {
      "limits": [
        {
          "counter": "views_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about views_update