sync_meetings · Fellow MCP Server MCP: Risk & Policy

WHAT IT DOES

What sync_meetings does on Fellow MCP Server

AI agents use sync_meetings to create or update resources in Fellow MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fellow MCP Server environment.

WHY IT NEEDS A POLICY

Why sync_meetings needs a policy

This tool writes data from the Fellow API into a local SQLite database. It creates or updates records (incremental or full re-sync), which is a reversible write operation. It does not delete data, execute code, or involve financial transactions. The blast radius is medium since a forced full re-sync could overwrite cached data, but the operation is fundamentally a data ingestion/update process.

From the tool's definition Sync meetings from Fellow API to local database. By default does incremental sync (only new/updated since last sync). Use force=true for full re-sync.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sync_meetings Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sync_meetings": {
      "limits": [
        {
          "counter": "sync_meetings_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Fellow MCP Server, so you can run agents against it safely.

FAQ

Questions about sync_meetings

What does the sync_meetings tool do? +

Sync meetings from Fellow API to local database. By default does incremental sync (only new/updated since last sync). Use force=true for full re-sync. It is categorised as a Write tool in the Fellow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on sync_meetings? +

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

What risk level is sync_meetings? +

sync_meetings is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit sync_meetings? +

Yes. Add a rate_limit block to the sync_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.

How do I block sync_meetings completely? +

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

What MCP server provides sync_meetings? +

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