AI agents use export_meeting to create or update resources in Fathom MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fathom MCP Server environment.
Export operations create or generate new data outputs without irreversibly deleting source data, placing this in the Write category. The severity is medium because while the data being exported is meeting information (potentially sensitive), the operation itself is reversible and does not modify or destroy the original meeting data.
From the tool's definition The tool name 'export_meeting' combined with the server's capability to 'export to markdown' indicates data extraction and transformation.
Documented attack patterns abuse exactly the kind of access export_meeting gives an agent:
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 export_meeting:
{
"version": "1",
"default": "deny",
"tools": {
"export_meeting": {
"limits": [
{
"counter": "export_meeting_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_meeting stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
export_meeting. It is categorised as a Write tool in the Fathom MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fathom MCP Server MCP server in PolicyLayer and add a rule for export_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.
export_meeting is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the export_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.
Set action: deny in the PolicyLayer policy for export_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.
export_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.
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.