find_songs_by_tags | PolicyLayer

WHAT IT DOES

What find_songs_by_tags does on Planning Center Online (PCO) MCP Server

AI agents call find_songs_by_tags 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.

THE RISK

Low Risk

Why find_songs_by_tags needs a policy

This tool searches and filters an existing dataset (songs) based on tag criteria. It performs no creation, modification, deletion, code execution, or financial operations. It is a straightforward data retrieval operation, similar to search or filter functions, making it a Read category risk.

From the tool's definition The tool 'find_songs_by_tags' retrieves or queries data about songs matching specified tags. The verb 'find' and the query-oriented functionality indicate a read-only operation with no side effects.

Documented attack patterns abuse exactly the kind of access find_songs_by_tags gives an agent:

POLICY

How to control find_songs_by_tags

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_songs_by_tags:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "find_songs_by_tags": {}
  }
}

find_songs_by_tags is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Planning Center Online (PCO) MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Planning Center Online (PCO) MCP Server tools

Write assign_tags_to_song Assign tags to a specific song. Write create_song Create a new song in Planning Center Online. Read find_song_by_title Find songs by title. Read get_all_arrangements_for_song Get a list of all the arrangements for a particular song from the Planning Center Online A Read get_arrangement_for_song Get information for a particular song from the Planning Center Online API. Read get_keys_for_arrangement_of_song Get a list of keys available for a particular song ID and arrangement ID from the Planning Read get_plan_items Fetch a list of items for a specific plan. Read get_plan_team_members Fetch a list of team members for a specific plan.

All 13 Planning Center Online (PCO) MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about find_songs_by_tags

What does the find_songs_by_tags tool do? +

Find songs that have all of the specified tags. 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.

How do I enforce a policy on find_songs_by_tags? +

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

What risk level is find_songs_by_tags? +

find_songs_by_tags is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit find_songs_by_tags? +

Yes. Add a rate_limit block to the find_songs_by_tags 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 find_songs_by_tags completely? +

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

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

Enforce policy on every Planning Center Online (PCO) MCP Server tool call.

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.

CHECK YOUR STACK →

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.