zoom_update_meeting

Update an existing meeting

SERVERSage MCP SOURCEsagemcp/sagemcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/zoom-update-meeting.md

WHAT IT DOES

What zoom_update_meeting does on Sage MCP

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

RISK

Why zoom_update_meeting is rated Medium

This tool modifies meeting details (time, title, participants, settings, etc.) but does not delete meetings or execute arbitrary code. The change is reversible (can be updated again).

From the tool's definition Tool name 'zoom_update_meeting' and description 'Update an existing meeting' indicate modification of meeting data. The verb 'update' is a reversible write operation that changes existing meeting parameters without deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs zoom_update_meeting safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For zoom_update_meeting, this is the rule to start with:

zoom_update_meeting Rate-limited

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

View as policy code

policy.json

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

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every zoom_update_meeting call is checked against it from then on.

FAQ

Questions about zoom_update_meeting

What does the zoom_update_meeting tool do? +

Update an existing meeting. It is categorised as a Write tool in the Sage MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on zoom_update_meeting? +

Register the Sage MCP server in PolicyLayer and add a rule for zoom_update_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 Sage MCP. Nothing to install.

What risk level is zoom_update_meeting? +

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

Can I rate-limit zoom_update_meeting? +

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

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

zoom_update_meeting is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →