AI agents call index_granola_transcripts to retrieve information from Recall without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though index_granola_transcripts only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
Index Granola meeting transcripts for semantic search. By default additive - only indexes new meetings. Use clearExisting to rebuild from scratch. It is categorised as a Read tool in the Recall MCP Server, which means it retrieves data without modifying state.
Register the Recall MCP server in PolicyLayer and add a rule for index_granola_transcripts: 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 Recall. Nothing to install.
index_granola_transcripts 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 index_granola_transcripts 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 index_granola_transcripts. 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.
index_granola_transcripts is provided by the Recall MCP server (thetenzinwoser/recall-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.