update_meeting_attendance
Mark (absent: true) or clear (absent: false) a guest
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/update-meeting-attendance.md
What update_meeting_attendance does on Max MCP Server
AI agents use update_meeting_attendance to create or update resources in Max MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Max MCP Server environment.
Why update_meeting_attendance is rated Medium
Reversibly updates meeting attendance status without deleting data or executing arbitrary code.
From the tool's definition Mark absent: true or clear absent: false a guest
Attacks that exploit this kind of access
The rule that runs update_meeting_attendance 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 update_meeting_attendance, this is the rule to start with:
update_meeting_attendance 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Max MCP Server, apply this rule, and every update_meeting_attendance call is checked against it from then on.
Questions about update_meeting_attendance
Mark (absent: true) or clear (absent: false) a guest. It is categorised as a Write tool in the Max MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Max MCP Server MCP server in PolicyLayer and add a rule for update_meeting_attendance: 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.
update_meeting_attendance 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 update_meeting_attendance 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 update_meeting_attendance. 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.
update_meeting_attendance 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.
More on Max MCP Server, and thousands of servers like it.
This server
Across the catalogue