Poll the async generation state of a version.
AI agents call roboflow_get_version_generation_status to retrieve information from Roboflow 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 the current generation status of a version asynchronously. It is a read-only operation with no side effects - it queries existing state without creating, modifying, deleting, or executing operations. The low severity reflects minimal risk: misuse would only retrieve status information, not compromise or alter data.
From the tool's definition Tool name 'roboflow_get_version_generation_status' and description 'Poll the async generation state of a version' indicate a query/retrieval operation that checks status without modifying data.
Attacks that exploit this kind of access
Poll the async generation state of a version. It is categorised as a Read tool in the Roboflow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Roboflow MCP Server MCP server in PolicyLayer and add a rule for roboflow_get_version_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 Roboflow MCP Server. Nothing to install.
roboflow_get_version_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 roboflow_get_version_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 roboflow_get_version_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.
roboflow_get_version_generation_status is provided by the Roboflow MCP Server MCP server (mayankd409/roboflow-mcp-server). 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 →