List locations (rooms) for a check-in event in Planning Center Check-Ins. Args: - event_id (string): The check-in event ID (get this from pco_list_checkin_events) - limit (number): Max results (1-100, default 25) - offset (number): Pagination offset (default 0) - response_format (
AI agents call pco_list_checkin_locations 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 and queries check-in location data from Planning Center Online without creating, modifying, deleting, or executing operations. It is a straightforward read operation with minimal blast radius if misused—at worst, an AI agent would retrieve location data it shouldn't have access to, but no data would be modified or destroyed.
From the tool's definition Tool description states 'List locations (rooms) for a check-in event' with parameters for pagination (limit, offset) but no modification or deletion capability. The word 'List' indicates a retrieval operation with no side effects.
Attacks that exploit this kind of access
List locations (rooms) for a check-in event in Planning Center Check-Ins. Args: - event_id (string): The check-in event ID (get this from pco_list_checkin_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_checkin_locations: 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_checkin_locations 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_checkin_locations 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_checkin_locations. 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_checkin_locations 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 →