Search for meetings/recordings in Fellow. Can filter by title, date range, or event ID. Returns a list of meetings with basic metadata.
AI agents call search_meetings to retrieve information from Fellow 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 meeting data from the Fellow.ai system with filters (title, date range, event ID) but does not create, modify, delete, or execute operations. It is purely a data retrieval/query operation with no side effects. The blast radius of misuse is minimal—an adversary could enumerate meetings they might not have access to, but cannot alter data or trigger actions. Classified as Read with low severity.
From the tool's definition Tool searches for meetings and returns basic metadata; no modification, deletion, or execution capabilities indicated. Description uses 'Search for' and 'Returns a list', consistent with query/retrieval operations.
Attacks that exploit this kind of access
Search for meetings/recordings in Fellow. Can filter by title, date range, or event ID. Returns a list of meetings with basic metadata. It is categorised as a Read tool in the Fellow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Fellow 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 Fellow MCP Server. Nothing to install.
search_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 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.
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.
search_meetings is provided by the Fellow MCP Server MCP server (liba2k/unofficial-fellow-mcp). 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 →