List dataset versions under a project.
AI agents call roboflow_list_versions 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 performs a straightforward read operation—it queries and returns a list of dataset versions associated with a project. It does not create, modify, delete, or execute any changes to the system. The action is purely informational retrieval with no destructive, financial, or code execution implications. Severity is low as misuse would only expose metadata about existing versions.
From the tool's definition Tool name 'roboflow_list_versions' and description 'List dataset versions under a project' indicate a query operation that retrieves information without modification or side effects.
Attacks that exploit this kind of access
List dataset versions under a project. 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_list_versions: 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_list_versions 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_list_versions 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_list_versions. 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_list_versions 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 →