Low Risk

get_meeting

get_meeting

How to control get_meeting ↓

What get_meeting does on Fathom MCP Server

AI agents call get_meeting to retrieve information from Fathom MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_meeting needs a policy

The 'get_meeting' tool retrieves meeting data from Fathom.video without modifying or deleting it. Despite the empty description, the naming convention ('get_'), the server's read-focused capabilities (transcripts, summaries, action items), and comparison with sibling tools strongly indicate this is a retrieval operation.

From the tool's definition Tool name 'get_meeting' and sibling tools context (get_transcript, get_action_items, list_meetings) indicate data retrieval.

Documented attack patterns abuse exactly the kind of access get_meeting gives an agent:

How to control get_meeting

PolicyLayer is an MCP gateway — it sits between your AI agents and Fathom MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_meeting:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_meeting": {}
  }
}

get_meeting is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Fathom MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_meeting

What does the get_meeting tool do? +

get_meeting. It is categorised as a Read tool in the Fathom MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_meeting? +

Register the Fathom MCP Server MCP server in PolicyLayer and add a rule for get_meeting: 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 Fathom MCP Server. Nothing to install.

What risk level is get_meeting? +

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

Can I rate-limit get_meeting? +

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

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

get_meeting is provided by the Fathom MCP Server MCP server (matthewbergvinson/fathom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Fathom MCP Server tool call.

Start from Fathom MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

11 Fathom MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.