Browse and retrieve meeting transcripts from Otter.ai. Operations: list (browse all), get (specific meeting), recent (last N days), stats (database info).
AI agents call meetings to retrieve information from Meeting Chief Lite without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'meetings' tool performs only data retrieval and querying operations—listing, fetching specific records, filtering by recency, and gathering statistics. These are classic Read category operations with no side effects, no data modification, and no ability to execute code or access other systems. The low severity reflects that misuse would only expose meeting transcript data, not modify or delete it.
From the tool's definition Tool description explicitly states operations are: list (browse all), get (specific meeting), recent (last N days), stats (database info). All are read-only retrieval operations with no modification or deletion capability.
Attacks that exploit this kind of access
Browse and retrieve meeting transcripts from Otter.ai. Operations: list (browse all), get (specific meeting), recent (last N days), stats (database info). It is categorised as a Read tool in the Meeting Chief Lite MCP Server, which means it retrieves data without modifying state.
Register the Meeting Chief Lite MCP server in PolicyLayer and add a rule for 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 Meeting Chief Lite. Nothing to install.
meetings 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 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.
Set action: deny in the PolicyLayer policy for 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.
meetings is provided by the Meeting Chief Lite MCP server (smcdonnell7/meeting-chief-lite). 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 →