Search for and list people in Planning Center People (PCO). Supports filtering by name, status, and more. Returns person records with attributes. Args: - query (string, optional): Search by name (partial match on first or last name) - where_first_name (string, optional): Filter by exact first nam...
AI agents call pco_list_people 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 people data from Planning Center Online without any side effects. It supports search and filter operations only, returning read-only person records. No data is created, modified, deleted, or executed.
From the tool's definition Tool name 'pco_list_people' and description 'Search for and list people' with filtering parameters (query, where_first_name, where_last_name, where_status) that 'Returns person records with attributes'.
Attacks that exploit this kind of access
Search for and list people in Planning Center People (PCO). Supports filtering by name, status, and more. Returns person records with attributes. Args: - query (string, optional): Search by name (partial match on first or last name) - where_first_name (string, optional): Filter by exact first name - where_last_name (string, optional): Filter by exact last name - where_status (string, optional): Filter by membership status (e.g. 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_people: 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_people 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_people 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_people. 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_people 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 →