get_meeting_summary

Get the meeting summary/notes content. Returns the structured notes including agenda items, discussion topics, and decisions made.

Server Fellow MCP Server liba2k/unofficial-fellow-mcp
Category Read
Risk class Low
Parameters 00 required

What get_meeting_summary does on Fellow MCP Server

AI agents call get_meeting_summary 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.

Why get_meeting_summary needs a policy

This tool retrieves and queries existing meeting summary data without modifying, deleting, or executing any operations. It is a straightforward read operation with no side effects. Severity is low because meeting notes are typically internal organizational data with limited blast radius if exposed.

From the tool's definition Tool name 'get_meeting_summary' and description 'Get the meeting summary/notes content. Returns the structured notes' indicates data retrieval only. No mutation, deletion, execution, or financial operations are described.

Questions about get_meeting_summary

What does the get_meeting_summary tool do? +

Get the meeting summary/notes content. Returns the structured notes including agenda items, discussion topics, and decisions made. It is categorised as a Read tool in the Fellow MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_meeting_summary? +

Register the Fellow MCP Server MCP server in PolicyLayer and add a rule for get_meeting_summary: 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.

What risk level is get_meeting_summary? +

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

Can I rate-limit get_meeting_summary? +

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

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

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

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