teams_call_history
Reads Microsoft Teams call & meeting history from the Mac's local Teams cache — no Graph API, no token, no admin consent (the same local store the Teams Calls tab renders). Each call includes direction (incoming/outgoing/missed), participants (names + ids), start / answered / end times, duration,...
This record as markdown: /tools/com-local-mcp-local-mcp/teams-call-history.md
What teams_call_history does on Local
AI agents call teams_call_history 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 calls to return (default 50), newest first |
since | string | — | Only calls on/after this date, YYYY-MM-DD (optional) |
until | string | — | Only calls on/before this date, YYYY-MM-DD (optional) |
Parameters from the server's own tool schema.
Why teams_call_history is rated Low
This tool only reads/retrieves call history data from a local cache with no side effects. However, severity is medium because call history (participants, times, durations) is sensitive metadata that could reveal communication patterns, relationships, and schedules if misused.
From the tool's definition Reads Microsoft Teams call & meeting history from the Mac's local Teams cache
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs teams_call_history 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_call_history, this is the rule to start with:
teams_call_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every teams_call_history call is checked against it from then on.
Questions about teams_call_history
Reads Microsoft Teams call & meeting history from the Mac's local Teams cache — no Graph API, no token, no admin consent (the same local store the Teams Calls tab renders). Each call includes direction (incoming/outgoing/missed), participants (names + ids), start / answered / end times, duration, call type (1:1/group/meeting) and a stable call id. Optional since/until (YYYY-MM-DD) narrow the range — e.g. a daily collector pulls the previous day's calls. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
teams_call_history accepts 3 parameters: limit, since, until. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for teams_call_history: 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.
teams_call_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the teams_call_history 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_call_history. 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_call_history 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.
More on Local, and thousands of servers like it.
This server
Across the catalogue