get_meeting_by_id

Fetch a single meeting document by ID, returning the full structured summary and metadata.

Server Granola MCP Server pavitarsaini/granola-mcp
Category Read
Risk class Low
Parameters 00 required

What get_meeting_by_id does on Granola MCP Server

AI agents call get_meeting_by_id to retrieve information from Granola MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_meeting_by_id needs a policy

This tool retrieves meeting data by ID without modifying, creating, deleting, or executing operations. The OAuth authentication ensures access control, but does not change the nature of the operation as a read query. Severity is low because unauthorized access to meeting notes, while potentially sensitive, does not cause irreversible data loss or financial impact.

From the tool's definition Tool name 'get_meeting_by_id' and description 'Fetch a single meeting document by ID, returning the full structured summary and metadata' indicate data retrieval with no modification or deletion. The verb 'fetch' confirms read-only access.

Questions about get_meeting_by_id

What does the get_meeting_by_id tool do? +

Fetch a single meeting document by ID, returning the full structured summary and metadata. It is categorised as a Read tool in the Granola MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_meeting_by_id? +

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

What risk level is get_meeting_by_id? +

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

Can I rate-limit get_meeting_by_id? +

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

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

get_meeting_by_id is provided by the Granola MCP Server MCP server (pavitarsaini/granola-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.