Fetch a specific section of the LiquidSoap 2.4.0 documentation
AI agents call get_documentation 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 and queries documentation content—a read-only operation with no side effects. It returns informational data about Liquidsoap without executing code, modifying data, or triggering external operations. The low severity reflects that documentation retrieval poses minimal risk even if accessed inappropriately.
From the tool's definition Tool name 'get_documentation' and description 'Fetch a specific section of the LiquidSoap 2.4.0 documentation' indicate retrieval of documentation data with no modification, creation, or execution of code.
Documented attack patterns abuse exactly the kind of access get_documentation 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_documentation:
{
"version": "1",
"default": "deny",
"tools": {
"get_documentation": {}
}
}get_documentation 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.
Fetch a specific section of the LiquidSoap 2.4.0 documentation. 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_documentation: 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_documentation 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_documentation 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_documentation. 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_documentation 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.