check_attendee_status
Checks the response status for attendees of a specific event.
This record as markdown: /tools/deciduus-calendar-mcp/check-attendee-status.md
What check_attendee_status does on Calendar
AI agents call check_attendee_status to retrieve information from Calendar without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_attendee_status is rated Low
This tool retrieves and reads attendee response statuses (accepted, declined, tentative, no response) for an event. It performs no data modification, deletion, or external operations. The operation has minimal blast radius even if misused by an agent—it only exposes calendar metadata about attendee responses, which is informational in nature.
From the tool's definition Tool name 'check_attendee_status' and description 'Checks the response status for attendees of a specific event' indicate a query operation that retrieves attendee information without modifying data.
Attacks that exploit this kind of access
The rule that runs check_attendee_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Calendar, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_attendee_status, this is the rule to start with:
check_attendee_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Calendar, apply this rule, and every check_attendee_status call is checked against it from then on.
Questions about check_attendee_status
Checks the response status for attendees of a specific event. It is categorised as a Read tool in the Calendar MCP Server, which means it retrieves data without modifying state.
Register the Calendar MCP server in PolicyLayer and add a rule for check_attendee_status: 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 Calendar. Nothing to install.
check_attendee_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_attendee_status 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 check_attendee_status. 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.
check_attendee_status is provided by the Calendar MCP server (deciduus/calendar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Calendar, and thousands of servers like it.
This server
Across the catalogue