Get a meeting by its ID. The meeting ID is a unique identifier for a meeting. It will return the meeting metadata, including the name, the date, the organizer, participants and more.
AI agents call get-meeting-metadata to retrieve information from tl;dv MCP for Zoom, Google Meet and MS Teams without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves meeting metadata through a query operation. It has no capability to modify, delete, or execute operations—it only fetches and returns existing meeting information. The blast radius of misuse is minimal, as an AI agent could only access metadata that users already have permission to view. This is a straightforward read operation.
From the tool's definition Tool description states it will 'Get a meeting by its ID' and 'return the meeting metadata, including the name, the date, the organizer, participants and more.' The verb 'Get' and the focus on retrieving metadata indicate a read-only operation with no…
Documented attack patterns abuse exactly the kind of access get-meeting-metadata gives an agent:
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. This is the rule we recommend for get-meeting-metadata:
{
"version": "1",
"default": "deny",
"tools": {
"get-meeting-metadata": {}
}
}get-meeting-metadata is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a meeting by its ID. The meeting ID is a unique identifier for a meeting. It will return the meeting metadata, including the name, the date, the organizer, participants and more. It is categorised as a Read tool in the tl;dv MCP for Zoom, Google Meet and MS Teams MCP Server, which means it retrieves data without modifying state.
Register the tl;dv MCP for Zoom, Google Meet and MS Teams MCP server in PolicyLayer and add a rule for get-meeting-metadata: 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 tl;dv MCP for Zoom, Google Meet and MS Teams. Nothing to install.
get-meeting-metadata 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 get-meeting-metadata 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 get-meeting-metadata. 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.
get-meeting-metadata is provided by the tl;dv MCP for Zoom, Google Meet and MS Teams MCP server (tldv-public/tldv-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from tl;dv MCP for Zoom, Google Meet and MS Teams, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
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.