Get a list of keys available for a particular song ID and arrangement ID from the Planning Center Online API.
AI agents call get_keys_for_arrangement_of_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 and retrieves music key information for a song arrangement from the Planning Center Online API. It performs a read-only operation that does not create, modify, delete, or execute any changes to data or external systems. The function is purely informational and returns a list of available keys, making it a Read category tool with low severity risk.
From the tool's definition Tool name 'get_keys_for_arrangement_of_song' and description 'Get a list of keys available' indicates a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_keys_for_arrangement_of_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_keys_for_arrangement_of_song:
{
"version": "1",
"default": "deny",
"tools": {
"get_keys_for_arrangement_of_song": {}
}
} get_keys_for_arrangement_of_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 a list of keys available for a particular song ID and arrangement ID 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_keys_for_arrangement_of_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_keys_for_arrangement_of_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_keys_for_arrangement_of_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_keys_for_arrangement_of_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_keys_for_arrangement_of_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.