teams_list_chats

Lists Microsoft Teams chats (direct messages and group chats).

SERVERLocal SOURCElocal-mcp

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-local-mcp-local-mcp/teams-list-chats.md

WHAT IT DOES

What teams_list_chats does on Local

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

Parameter	Type	Required	Description
`limit`	integer	—	Max chats to return (default 50)

Parameters from the server's own tool schema.

RISK

Why teams_list_chats is rated Low

This tool retrieves and queries Teams chat metadata without creating, modifying, or deleting data. It is a Read operation. Severity is medium rather than low because Teams chats may contain sensitive business communications, making unauthorized listing a privacy concern in a system where an AI agent could access user data without proper authorization controls.

From the tool's definition Tool name 'teams_list_chats' and description 'Lists Microsoft Teams chats' indicate retrieval/enumeration of chat data with no modification or deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs teams_list_chats 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_list_chats, this is the rule to start with:

teams_list_chats Allowed

teams_list_chats 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_list_chats": {}
  }
}

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

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

FAQ

Questions about teams_list_chats

What does the teams_list_chats tool do? +

Lists Microsoft Teams chats (direct messages and group chats). It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.

What parameters does teams_list_chats accept? +

teams_list_chats accepts 1 parameter: limit. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on teams_list_chats? +

Register the Local MCP server in PolicyLayer and add a rule for teams_list_chats: 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_list_chats? +

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

Can I rate-limit teams_list_chats? +

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

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

teams_list_chats 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

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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