teams_send_message

SERVERLocal SOURCElocal-mcp

Medium RISK CLASS

Category Write

Parameters 32 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-local-mcp-local-mcp/teams-send-message.md

WHAT IT DOES

What teams_send_message does on Local

AI agents use teams_send_message to create or update resources in Local, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local environment.

Parameter	Type	Required	Description
`text`	string	Yes	Plain-text message body. Max 28000 chars. No formatting / mentions / attachments in v1.
`chat_id`	string	Yes	Thread id from teams_list_chats (e.g. '19:<uuid>_<uuid>@unq.gbl.spaces' for 1:1, '19:<uuid>@thread.tacv2' for group)
`confirm`	boolean	—	Must be true to actually send. Without it, returns a preview without making any network call.

Parameters from the server's own tool schema.

RISK

Why teams_send_message is rated Medium

This tool creates new data (Teams messages) in a reversible manner. While sending messages could have business consequences, the operation itself is Write rather than Execute (no arbitrary code execution) or Destructive (messages can be deleted).

From the tool's definition Tool description explicitly states "Sends a text message to a Microsoft Teams chat or channel" and "This is a write operation". The confirmation pattern (preview on first call, send on second with confirm=true) indicates reversible message creation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs teams_send_message safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For teams_send_message, this is the rule to start with:

teams_send_message Rate-limited

teams_send_message stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "teams_send_message": {
      "limits": [
        {
          "counter": "teams_send_message_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every teams_send_message call is checked against it from then on.

FAQ

Questions about teams_send_message

What does the teams_send_message tool do? +

Sends a text message to a Microsoft Teams chat or channel. Requires Microsoft Teams to be running and signed in (token is read fresh from Teams' local cookies on each call). The chat_id MUST come from a previous teams_list_chats call — never fabricate ids. This is a write operation: the first call returns a preview, the second call (with confirm=true) actually sends. It is categorised as a Write tool in the Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does teams_send_message accept? +

teams_send_message accepts 3 parameters: text, chat_id, confirm. Required: text, chat_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on teams_send_message? +

Register the Local MCP server in PolicyLayer and add a rule for teams_send_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 Local. Nothing to install.

What risk level is teams_send_message? +

teams_send_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit teams_send_message? +

Yes. Add a rate_limit block to the teams_send_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.

How do I block teams_send_message completely? +

Set action: deny in the PolicyLayer policy for teams_send_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.

What MCP server provides teams_send_message? +

teams_send_message is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Local, and thousands of servers like it.

This server

All 234 Local tools →

Across the catalogue

sms_send on Twilio SMS MCP Server →send-draft on Meme MCP Server →mail_send_draft on Apple Apps MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →