List check-in records in Planning Center Check-Ins. Args: - where_created_after (string, optional): Filter check-ins created after this date (YYYY-MM-DD) - where_created_before (string, optional): Filter check-ins created before this date (YYYY-MM-DD) - limit (number): Max results (1-100, default...
AI agents call pco_list_checkins 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 lists existing check-in records with optional filtering and pagination. It has no side effects, does not modify data, and produces no irreversible changes. It is a straightforward Read operation with minimal security risk when misused by an AI agent, as the worst outcome is unauthorized access to attendance records, which are typically less sensitive than personal or financial data.
From the tool's definition Tool name 'pco_list_checkins' and description 'List check-in records' indicate a query/retrieval operation. Arguments are all read-only filters (date ranges, pagination limits, offset) with no parameters for creating, modifying, or deleting data.
Attacks that exploit this kind of access
List check-in records in Planning Center Check-Ins. Args: - where_created_after (string, optional): Filter check-ins created after this date (YYYY-MM-DD) - where_created_before (string, optional): Filter check-ins created before this date (YYYY-MM-DD) - 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_checkins: 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_checkins 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_checkins 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_checkins. 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_checkins 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 →