AI agents use canvases_edit 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 canvas data in Slack, which is reversible (can be edited again or reverted). It does not delete data (would be Destructive) or execute arbitrary code (would be Execute), but it does allow an AI agent to alter shared workspace content that other users may depend on. High severity due to potential for unintended modifications to collaborative documents that could impact team workflows.
From the tool's definition Tool name 'canvases_edit' and description 'Edit a canvas' indicate modification of existing data. The Slack API documentation confirms canvases.edit modifies canvas content, making this a reversible write operation.
Attacks that exploit this kind of access
Edit a canvas. 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 canvases_edit: 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.
canvases_edit 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 canvases_edit 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 canvases_edit. 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.
canvases_edit 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 →