AI agents use send_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 creates new messages in Teams channels. While message creation is reversible (messages can be deleted via sibling tools like delete_channel_message), the primary action is to write/create data. The blast radius is medium because a misbehaving agent could spam channels, send misleading information, or @mention entire teams, but cannot directly delete data or cause financial harm.
From the tool's definition Tool description states 'Send a message to a specific channel' which creates new message data. The capability to send formatted messages with mentions and importance levels demonstrates irreversible content creation.
Attacks that exploit this kind of access
Send a message to a specific channel in a Microsoft Team. Supports text and markdown formatting, mentions, and importance levels. 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 send_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.
send_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 send_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 send_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.
send_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.