AI agents use reply_to_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 a new reply message in a Teams channel, which is a reversible write operation. It does not delete, execute code, or involve financial transactions. Misuse could lead to unwanted messages or mentions being posted on behalf of a user, hence medium severity.
From the tool's definition Reply to a specific message in a channel. Supports text and markdown formatting, mentions, and importance levels.
Attacks that exploit this kind of access
Reply to a specific message in a channel. 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 reply_to_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.
reply_to_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 reply_to_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 reply_to_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.
reply_to_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.