Check the status of a running pipeline. Call this after starting any auto_ pipeline
AI agents call check_pipeline_status to retrieve information from AudacityMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the state of an existing pipeline without creating, modifying, executing, or deleting anything. It is purely informational—a status check operation with no side effects. This is a classic Read operation.
From the tool's definition The tool is named 'check_pipeline_status' and described as checking the status of a running pipeline with no modification or execution capabilities. It only retrieves state information.
Documented attack patterns abuse exactly the kind of access check_pipeline_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AudacityMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for check_pipeline_status:
{
"version": "1",
"default": "deny",
"tools": {
"check_pipeline_status": {}
}
}check_pipeline_status 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.
Check the status of a running pipeline. Call this after starting any auto_ pipeline. It is categorised as a Read tool in the AudacityMCP MCP Server, which means it retrieves data without modifying state.
Register the Audacity MCP server in PolicyLayer and add a rule for check_pipeline_status: 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 AudacityMCP. Nothing to install.
check_pipeline_status 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 check_pipeline_status 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 check_pipeline_status. 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.
check_pipeline_status is provided by the Audacity MCP server (xdarkzx/audacity-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 131 AudacityMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
131 AudacityMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.