Get information for a particular song from the Planning Center Online API.
AI agents call get_arrangement_for_song to retrieve information from Planning Center Online (PCO) MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries song arrangement data from a church management system. It performs a retrieval operation without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an agent could retrieve unwanted data but cannot harm the system or data integrity. Church song metadata is not sensitive financial or destructive information.
From the tool's definition Tool name is 'get_arrangement_for_song' and description states it retrieves information for a song from the Planning Center Online API. The verb 'get' and action 'retrieve information' indicate a read-only operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_arrangement_for_song gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Planning Center Online (PCO) MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_arrangement_for_song:
{
"version": "1",
"default": "deny",
"tools": {
"get_arrangement_for_song": {}
}
} get_arrangement_for_song is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get information for a particular song from the Planning Center Online API. It is categorised as a Read tool in the Planning Center Online (PCO) MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Planning Center Online (PCO) MCP Server MCP server in PolicyLayer and add a rule for get_arrangement_for_song: 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 (PCO) MCP Server. Nothing to install.
get_arrangement_for_song 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 get_arrangement_for_song 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 get_arrangement_for_song. 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.
get_arrangement_for_song is provided by the Planning Center Online (PCO) MCP Server MCP server (jake-ccnh/pco-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Planning Center Online (PCO) MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 Planning Center Online (PCO) MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.