AI agents use update_channel_message to create or update resources in Teams — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Teams environment.
This tool modifies existing channel messages reversibly. It is a Write operation because it changes data (message content) without deletion or destruction. Severity is medium because an AI agent with this capability could modify messages to spread misinformation, impersonate the original sender's intent, or disrupt team communications—but the changes are reversible and limited to the agent's own or authorized…
From the tool's definition Tool name is 'update_channel_message' and description states 'Update (edit) a message in a channel that was previously sent.' The verb 'update' and 'edit' indicate modification of existing data.
Attacks that exploit this kind of access
Update (edit) a message in a channel that was previously sent. Only the message sender can update their own messages. It is categorised as a Write tool in the Teams MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Teams MCP server in PolicyLayer and add a rule for update_channel_message: 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 Teams. Nothing to install.
update_channel_message 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 update_channel_message 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 update_channel_message. 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.
update_channel_message is provided by the Teams MCP server (@floriscornel/teams-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.