AI agents call get_show 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.
No description provided, but the tool name 'get_show', the 'get_' prefix pattern across all sibling tools, and the read-only nature of the underlying Phish fan databases (setlists, reviews, audio metadata) strongly suggest this is a data retrieval function with no side effects. Confidence is slightly reduced due to empty description, but the pattern is clear.
From the tool's definition Tool name 'get_show' combined with sibling tools like 'get_audio', 'get_reviews', 'get_song', 'search_shows' and server context (phish.net/phish.in APIs for setlists, songs, jam-charts) indicates this retrieves data about shows without modification.
Attacks that exploit this kind of access
get_show. 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 get_show: 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.
get_show 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_show 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_show. 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_show 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 →