Find meetings that included specific participants. Searches the local database.
AI agents call get_meetings_by_participants 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 records based on participant criteria from a local cached database. It has no side effects—it does not create, modify, delete, or execute any operations. The search operation is read-only and reversible.
From the tool's definition Tool description states it 'Find meetings that included specific participants. Searches the local database.' The action is purely retrieval/search with no modification or deletion of data.
Attacks that exploit this kind of access
Find meetings that included specific participants. Searches the local database. 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 get_meetings_by_participants: 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.
get_meetings_by_participants 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_meetings_by_participants 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_meetings_by_participants. 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_meetings_by_participants 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 →