# check_attendee_status

Checks the response status for attendees of a specific event.

Agent View of the PolicyLayer registry record for `check_attendee_status`. HTML page: https://policylayer.com/tools/deciduus-calendar-mcp/check-attendee-status

## Facts

- Tool: `check_attendee_status`
- Server: Calendar (`deciduus/calendar-mcp`) — https://policylayer.com/tools/deciduus-calendar-mcp.md
- Homepage: https://github.com/deciduus/calendar-mcp
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "check_attendee_status",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Calendar:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_attendee_status": {}
  }
}
```

## Other tools on Calendar (11)

- `delete_event` — Destructive — https://policylayer.com/tools/deciduus-calendar-mcp/delete-event.md
- `analyze_busyness` — Read — https://policylayer.com/tools/deciduus-calendar-mcp/analyze-busyness.md
- `find_events` — Read — https://policylayer.com/tools/deciduus-calendar-mcp/find-events.md
- `list_calendars` — Read — https://policylayer.com/tools/deciduus-calendar-mcp/list-calendars.md
- `query_free_busy` — Read — https://policylayer.com/tools/deciduus-calendar-mcp/query-free-busy.md
- `add_attendee` — Write — https://policylayer.com/tools/deciduus-calendar-mcp/add-attendee.md
- `create_calendar` — Write — https://policylayer.com/tools/deciduus-calendar-mcp/create-calendar.md
- `create_event` — Write — https://policylayer.com/tools/deciduus-calendar-mcp/create-event.md
- `quick_add_event` — Write — https://policylayer.com/tools/deciduus-calendar-mcp/quick-add-event.md
- `schedule_mutual` — Write — https://policylayer.com/tools/deciduus-calendar-mcp/schedule-mutual.md
- `update_event` — Write — https://policylayer.com/tools/deciduus-calendar-mcp/update-event.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=deciduus-calendar-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/deciduus-calendar-mcp