// MCP SERVER RECORD

Microsoft Teams

Unverified
NPMmicrosoft-teams-mcp-server
BRisk grademodest
Catalogue entry updated 7 days ago
Auth postureNot probedno remote endpoint probed yet
Tools113 Write · 8 Read
Worst categoryWritegrade tracks the peak, not the average
Capability mix
Write 3Read 8
What it can reach
Ingests untrusted inputTouches secretsReaches networkRuns codeTouches filesChanges permissionsSends external commsPersistsDeletes dataMoves money
Exfiltration pathReads content an attacker can plant and can send data outward — a prompt-injection-to-exfiltration route.
Tools 11
teams_reply_to_messageWriteMediumteams_send_channel_messageWriteMediumteams_send_chat_messageWriteMediumteams_get_profileReadLowteams_list_channelsReadLow
View all 11 tools
teams_list_chatsReadLowteams_list_teamsReadLowteams_read_channel_messagesReadLowteams_read_chat_messagesReadLowteams_read_message_repliesReadLowteams_search_messagesReadHigh
Change history
No changes recorded since first scan. Watched servers surface a diff within the hour.
Recommended policy
teams_reply_to_messagerate limit
Read-only toolsallow
Full policy breakdown with enforcement rules →
// RUNNING THIS SERVER
DIRECT INSTALL npx -y microsoft-teams-mcp-server

Installed this way, nothing enforces the recommended policy above — calls run exactly as the agent makes them.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.