Create a new person record in Planning Center People. Args: - first_name (string, required): First name - last_name (string, required): Last name - middle_name (string, optional): Middle name - birthdate (string, optional): Birthdate in YYYY-MM-DD format - gender (string, optional): Gender (
AI agents use pco_create_person to create or update resources in Planning Center Online MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Planning Center Online MCP Server environment.
This tool creates a new person record in a People Management system, which is a reversible write operation. It does not delete data (not Destructive), does not involve financial transactions (not Financial), and does not execute arbitrary code (not Execute).
From the tool's definition Tool name is 'pco_create_person' and description states 'Create a new person record in Planning Center People.' The arguments include first_name, last_name, middle_name, birthdate, and gender—all parameters for creating a new data record.
Attacks that exploit this kind of access
Create a new person record in Planning Center People. Args: - first_name (string, required): First name - last_name (string, required): Last name - middle_name (string, optional): Middle name - birthdate (string, optional): Birthdate in YYYY-MM-DD format - gender (string, optional): Gender (. It is categorised as a Write tool in the Planning Center Online MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Planning Center Online MCP Server MCP server in PolicyLayer and add a rule for pco_create_person: 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_create_person is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the pco_create_person 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_create_person. 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_create_person 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 →