Get the changelog and breaking changes for LiquidSoap 2.4.0
AI agents call get_changelog to retrieve information from LiquidSoapMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical information about changes in Liquidsoap version 2.4.0. It is a pure read operation that queries existing documentation without creating, modifying, deleting, executing code, or committing any financial obligations. The low severity reflects the benign nature of accessing public reference material.
From the tool's definition Tool name 'get_changelog' and description 'Get the changelog and breaking changes for LiquidSoap 2.4.0' indicate retrieval of documentation/version history with no modifications, deletions, or side effects.
Documented attack patterns abuse exactly the kind of access get_changelog gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LiquidSoapMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_changelog:
{
"version": "1",
"default": "deny",
"tools": {
"get_changelog": {}
}
}get_changelog is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the changelog and breaking changes for LiquidSoap 2.4.0. It is categorised as a Read tool in the LiquidSoapMCP MCP Server, which means it retrieves data without modifying state.
Register the LiquidSoap MCP server in PolicyLayer and add a rule for get_changelog: 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 LiquidSoapMCP. Nothing to install.
get_changelog 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_changelog 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_changelog. 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_changelog is provided by the LiquidSoap MCP server (splinesreticulating/liquidsoapmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LiquidSoapMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 LiquidSoapMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.