List songs in the Planning Center Services song library. Args: - query (string, optional): Search songs by title - hidden (boolean, optional): Filter by hidden status (true = hidden, false = visible only) - limit (number): Max results (1-100, default 25) - offset (number): Pagination offset (defa...
AI agents call pco_list_songs to retrieve information from Planning Center Online MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data from the Planning Center Services song library without side effects. It performs a simple read operation with optional filtering and pagination, fitting the Read category (search, list, get, fetch). The blast radius is minimal—incorrect queries return no results or filtered results without affecting system state.
From the tool's definition The tool is described as 'List songs' with search capability by title and filtering by visibility status. It includes pagination parameters (limit, offset) typical of list/query operations. There is no modification, deletion, execution, or financial component.
Attacks that exploit this kind of access
List songs in the Planning Center Services song library. Args: - query (string, optional): Search songs by title - hidden (boolean, optional): Filter by hidden status (true = hidden, false = visible only) - limit (number): Max results (1-100, default 25) - offset (number): Pagination offset (default 0) - response_format (. It is categorised as a Read tool in the Planning Center Online MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Planning Center Online MCP Server MCP server in PolicyLayer and add a rule for pco_list_songs: 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_list_songs 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 pco_list_songs 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_list_songs. 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_list_songs 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 →