Get detailed information about a specific meeting
AI agents call get_meeting_details 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.
This tool retrieves and queries meeting information without creating, modifying, deleting, or executing any side effects. It is a straightforward data retrieval tool with minimal risk if misused by an AI agent—the worst outcome would be accessing meeting data the user already has permission to view.
From the tool's definition Tool name is 'get_meeting_details' and description states 'Get detailed information about a specific meeting'. The verb 'get' and lack of any modification, deletion, or execution language indicate this is a retrieval operation.
Attacks that exploit this kind of access
Get detailed information about a specific meeting. It is categorised as a Read tool in the Granola MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Granola MCP Server MCP server in PolicyLayer and add a rule for get_meeting_details: 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.
get_meeting_details 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_details 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_details. 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_details is provided by the Granola MCP Server MCP server (maxgerlach1/granola-ai-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →