AI agents call search_shows to retrieve information from Mcp Phish without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Search operations retrieve data without modification or side effects. The tool fits the Read category pattern alongside other sibling search/get tools on the music metadata server. Confidence is slightly reduced because the tool description is empty, but the name and server context strongly indicate a read-only search function. No data is created, modified, deleted, or financial action is taken.
From the tool's definition Tool name 'search_shows' indicates a query/search operation. Server context describes tools for 'setlists, songs, jam-charts, reviews, and audio'—all retrieval operations.
Attacks that exploit this kind of access
search_shows. It is categorised as a Read tool in the Mcp Phish MCP Server, which means it retrieves data without modifying state.
Register the Mcp Phish MCP server in PolicyLayer and add a rule for search_shows: 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 Mcp Phish. Nothing to install.
search_shows 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 search_shows 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 search_shows. 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.
search_shows is provided by the Mcp Phish MCP server (pete-builds/mcp-phish). 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 →