List specific instances (occurrences) of a calendar event. Args: - event_id (string): The calendar event ID (get this from pco_list_calendar_events) - limit (number): Max results (1-100, default 25) - offset (number): Pagination offset (default 0) - response_format (
AI agents call pco_list_event_instances to retrieve information from Planning Center Online MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves calendar event instances from Planning Center Online without modifying, executing, or deleting any data. It is a read-only query operation with minimal blast radius if misused by an agent—the worst outcome would be accessing calendar event occurrences the agent should not see, a data exposure risk but not destructive or operational.
From the tool's definition Tool name contains 'list' and description states 'List specific instances (occurrences) of a calendar event.' The arguments support pagination (limit, offset) typical of query operations with no mutation capabilities.
Attacks that exploit this kind of access
List specific instances (occurrences) of a calendar event. Args: - event_id (string): The calendar event ID (get this from pco_list_calendar_events) - limit (number): Max results (1-100, default 25) - offset (number): Pagination offset (default 0) - response_format (. It is categorised as a Read tool in the Planning Center Online MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Planning Center Online MCP Server MCP server in PolicyLayer and add a rule for pco_list_event_instances: 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 Planning Center Online MCP Server. Nothing to install.
pco_list_event_instances 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 pco_list_event_instances 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 pco_list_event_instances. 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.
pco_list_event_instances is provided by the Planning Center Online MCP Server MCP server (tracsoftllc/pco-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →