AI agents use teams_chat_send to create or update resources in Outpost — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Outpost environment.
This tool creates new data (chat messages) in a reversible manner. While the message cannot be unsent in practice, the tool itself doesn't delete or overwrite existing data, execute arbitrary code, or involve financial transactions. The medium severity reflects that an AI agent could spam, impersonate, or harass users via Teams, but the impact is limited to disruption rather than data loss or financial harm.
From the tool's definition Tool description explicitly states 'Send a message to a Teams chat (1:1 or group)', which is a create/post action that adds new data (a chat message) to a communication channel.
Attacks that exploit this kind of access
Send a message to a Teams chat (1:1 or group). It is categorised as a Write tool in the Outpost MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Outpost MCP server in PolicyLayer and add a rule for teams_chat_send: 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 Outpost. Nothing to install.
teams_chat_send 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 teams_chat_send 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 teams_chat_send. 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.
teams_chat_send is provided by the Outpost MCP server (signalclaude/outpost). 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 →