search_meetings

Keyword search across meeting titles and summaries. Returns matching meetings with key metadata.

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

What search_meetings does on Granola MCP Server

AI agents call search_meetings 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 search_meetings needs a policy

This tool retrieves and queries data from the Granola meeting notes system without creating, modifying, deleting, or executing any operations. It is a passive search function that returns results only. The most restrictive action is reading data, making it a Read category tool with low severity—accidental or malicious misuse would retrieve information but cannot cause irreversible harm or side effects.

From the tool's definition Tool performs 'keyword search across meeting titles and summaries' and 'returns matching meetings with key metadata.' The description uses retrieval language ('search', 'returns') with no mention of modification, deletion, or execution capabilities.

Questions about search_meetings

What does the search_meetings tool do? +

Keyword search across meeting titles and summaries. Returns matching meetings with key 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 search_meetings? +

Register the Granola MCP Server MCP server in PolicyLayer and add a rule for search_meetings: 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 search_meetings? +

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

Can I rate-limit search_meetings? +

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

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

search_meetings 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.