This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/radio-by-tag.md
What radio_by_tag does on UnClick
AI agents call radio_by_tag to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
tag | string | Yes | |
limit | number | — |
Parameters from the server's own tool schema.
Why radio_by_tag is rated Low
This tool retrieves information about radio stations filtered by genre tag. It performs a search or lookup operation that returns data without modifying, deleting, or executing external operations. The 'Get' verb and read-only nature of querying a radio station directory place it firmly in the Read category with low severity.
From the tool's definition Tool name 'radio_by_tag' and description 'Get radio stations by genre tag' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs radio_by_tag safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For radio_by_tag, this is the rule to start with:
radio_by_tag is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every radio_by_tag call is checked against it from then on.
Questions about radio_by_tag
Get radio stations by genre tag. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
radio_by_tag accepts 2 parameters: tag, limit. Required: tag. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for radio_by_tag: 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 UnClick. Nothing to install.
radio_by_tag 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 radio_by_tag 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 radio_by_tag. 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.
radio_by_tag is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue