get_upcoming_meetings

List upcoming meetings (excluding cancelled/rejected) ordered by start time ascending. from defaults to now and to defaults to now + 30 days (both ISO8601). Returns {data: meeting row[]} (status one of pending|scheduled|rescheduled|completed|no_show; pending = awaiting confirm_meeting / decline_m...

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

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/digital-crew-technologies-max-mcp-server/get-upcoming-meetings.md

WHAT IT DOES

What get_upcoming_meetings does on Max MCP Server

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

RISK

Why get_upcoming_meetings is rated Low

Tool retrieves meeting data without modifying or deleting any information; pure query operation.

From the tool's definition List upcoming meetings, returns meeting row data, read-only query

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_upcoming_meetings 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 get_upcoming_meetings, this is the rule to start with:

get_upcoming_meetings Allowed

get_upcoming_meetings is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_upcoming_meetings": {}
  }
}

ALLOW ONLY 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 get_upcoming_meetings call is checked against it from then on.

FAQ

Questions about get_upcoming_meetings

What does the get_upcoming_meetings tool do? +

How do I enforce a policy on get_upcoming_meetings? +

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

What risk level is get_upcoming_meetings? +

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

Can I rate-limit get_upcoming_meetings? +

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

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

get_upcoming_meetings 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 →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →