// SCAN REPORT

tl;dv MCP for Zoom, Google Meet and MS Teams

4 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 12 Jun 2026

0 can modify or destroy data

4 read-only

4 tools total

Community server · catalogue entry verified 12/06/2026

How to control tl;dv MCP for Zoom, Google Meet and MS Teams ↓

TOOL MAP

What tl;dv MCP for Zoom, Google Meet and MS Teams exposes to your agents

Read (4) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control tl;dv MCP for Zoom, Google Meet and MS Teams

PolicyLayer is an MCP gateway — it sits between your AI agents and tl;dv MCP for Zoom, Google Meet and MS Teams, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "get-highlights": {
    "limits": [
      {
        "counter": "get-highlights_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register tl;dv MCP for Zoom, Google Meet and MS Teams — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON TL;DV MCP FOR ZOOM, GOOGLE MEET AND MS TEAMS →

Free to start. No card required.

FULL CATALOGUE

All 4 tl;dv MCP for Zoom, Google Meet and MS Teams tools

READ 4 tools

Read get-highlights Allows you to get highlights from a meeting by providing a meeting ID. Read get-meeting-metadata Get a meeting by its ID. The meeting ID is a unique identifier for a meeting. It will return the meeting metad Read get-transcript Get transcript by meeting ID. The transcript is a list of messages exchanged between the participants in the m Read list-meetings List all meetings based on the filters provided. You can filter by date, status, and more. Those meetings are

FAQ

Questions about tl;dv MCP for Zoom, Google Meet and MS Teams

Is the tl;dv MCP for Zoom, Google Meet and MS Teams MCP server safe to use without restrictions? +

The tl;dv MCP for Zoom, Google Meet and MS Teams server is primarily read-only with 4 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the tl;dv MCP for Zoom, Google Meet and MS Teams MCP server expose? +

4 tools across 1 categories: Read. 4 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on tl;dv MCP for Zoom, Google Meet and MS Teams? +

Register the tl;dv MCP for Zoom, Google Meet and MS Teams MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every tl;dv MCP for Zoom, Google Meet and MS Teams tool call.

Deterministic rules across all 4 tl;dv MCP for Zoom, Google Meet and MS Teams tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON TL;DV MCP FOR ZOOM, GOOGLE MEET AND MS TEAMS →

Free to start. No card required.

4 tl;dv MCP for Zoom, Google Meet and MS Teams tools catalogued and risk-classified — across an index of 43,000+ MCP servers.