AI agents call find_song_by_title 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 performs a simple read-only search operation across the song database, matching queries against song titles. It retrieves information but does not create, modify, delete, or execute any actions. The operation has no side effects and minimal blast radius if misused by an agent.
From the tool's definition Tool name 'find_song_by_title' and description 'Find songs by title' indicate a search/query operation that retrieves data without modifying or deleting anything.
Documented attack patterns abuse exactly the kind of access find_song_by_title 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 find_song_by_title:
{
"version": "1",
"default": "deny",
"tools": {
"find_song_by_title": {}
}
} find_song_by_title 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.
Find songs by title. 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 find_song_by_title: 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.
find_song_by_title 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 find_song_by_title 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 find_song_by_title. 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.
find_song_by_title 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.