teams_search_messages

Search across messages in the user

SERVERSage MCP SOURCEsagemcp/sagemcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/teams-search-messages.md

WHAT IT DOES

What teams_search_messages does on Sage MCP

AI agents call teams_search_messages to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why teams_search_messages is rated Low

This is a Read operation: it searches and retrieves messages from Microsoft Teams, producing no side effects. Severity is high rather than low because message content often contains sensitive information (credentials, personal data, business intelligence), making unauthorized search access a significant data exposure risk despite being read-only.

From the tool's definition Tool name is 'teams_search_messages' and description states 'Search across messages in the user' — this retrieves/queries message data without modifying it.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs teams_search_messages safely

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

teams_search_messages Allowed

teams_search_messages is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "teams_search_messages": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about teams_search_messages

What does the teams_search_messages tool do? +

Search across messages in the user. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on teams_search_messages? +

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

What risk level is teams_search_messages? +

teams_search_messages is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit teams_search_messages? +

Yes. Add a rate_limit block to the teams_search_messages 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_search_messages completely? +

Set action: deny in the PolicyLayer policy for teams_search_messages. 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_search_messages? +

teams_search_messages is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →