decline_meeting

Reject a pending Cal.com booking request by meeting_id, with an optional reason. Irreversible; Cal.com notifies the attendee. Returns {data: meeting row} with status

SERVERMax MCP Server SOURCEdigital-crew-technologies/max-mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/digital-crew-technologies-max-mcp-server/decline-meeting.md

WHAT IT DOES

What decline_meeting does on Max MCP Server

AI agents call decline_meeting to permanently remove resources in Max MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why decline_meeting is rated Critical

Irreversibly declines meetings, cannot be recovered once processed by Cal.com system.

From the tool's definition Reject pending booking, irreversible, notifies attendee, cannot be undone

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs decline_meeting safely

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

decline_meeting Hidden

decline_meeting is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "decline_meeting"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about decline_meeting

What does the decline_meeting tool do? +

Reject a pending Cal.com booking request by meeting_id, with an optional reason. Irreversible; Cal.com notifies the attendee. Returns {data: meeting row} with status. It is categorised as a Destructive tool in the Max MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on decline_meeting? +

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

What risk level is decline_meeting? +

decline_meeting is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit decline_meeting? +

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

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

decline_meeting is provided by the Max MCP Server MCP server (digital-crew-technologies/max-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Max MCP Server, and thousands of servers like it.

This server

All 415 Max MCP Server tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →