pco_update_person · Planning Center Online MCP Server MCP

WHAT IT DOES

What pco_update_person does on Planning Center Online MCP Server

AI agents use pco_update_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.

WHY IT NEEDS A POLICY

Why pco_update_person needs a policy

This tool creates or modifies data reversibly using PATCH semantics. It updates person records in Planning Center Online without deleting or destroying data, and does not execute arbitrary code or move money.

From the tool's definition Tool name 'pco_update_person' and description states 'Update an existing person record' with 'sparse update / PATCH semantics', modifying fields like first_name, last_name, middle_name, birthdate, and gender.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pco_update_person Rate-limited

pco_update_person stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pco_update_person": {
      "limits": [
        {
          "counter": "pco_update_person_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Planning Center Online MCP Server, so you can run agents against it safely.

FAQ

Questions about pco_update_person

What does the pco_update_person tool do? +

Update an existing person record in Planning Center People. Only the fields you provide will be updated (sparse update / PATCH semantics). Args: - id (string): PCO person ID to update - first_name (string, optional): Updated first name - last_name (string, optional): Updated last name - middle_name (string, optional): Updated middle name - birthdate (string, optional): Updated birthdate in YYYY-MM-DD format - gender (string, optional): Updated 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.

How do I enforce a policy on pco_update_person? +

Register the Planning Center Online MCP Server MCP server in PolicyLayer and add a rule for pco_update_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.

What risk level is pco_update_person? +

pco_update_person is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit pco_update_person? +

Yes. Add a rate_limit block to the pco_update_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.

How do I block pco_update_person completely? +

Set action: deny in the PolicyLayer policy for pco_update_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.

What MCP server provides pco_update_person? +

pco_update_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.