check_generation_status
AI agents call check_generation_status to retrieve information from AudioGen MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about generation processes—a read operation with no side effects. It fits the pattern of query/get/list operations that retrieve data. No data creation, modification, deletion, code execution, or financial impact is indicated. Low severity because status checks cannot cause harm even if misused.
From the tool's definition Tool name 'check_generation_status' indicates status querying. Sibling tools include 'get_model_status' and 'list_generation_jobs', which are clearly read operations.
Attacks that exploit this kind of access
check_generation_status. It is categorised as a Read tool in the AudioGen MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AudioGen MCP Server MCP server in PolicyLayer and add a rule for check_generation_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 AudioGen MCP Server. Nothing to install.
check_generation_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_generation_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_generation_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_generation_status is provided by the AudioGen MCP Server MCP server (peerjakobsen/audiogen-mcp). 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 →