List the workspace accessible with the current API key.
AI agents call list_workspaces 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 and enumerates workspace information accessible to the authenticated user. It performs no data creation, modification, deletion, or execution of external operations. It is a straightforward read-only query operation with minimal risk if misused by an AI agent, as it only returns metadata about available workspaces.
From the tool's definition Tool name 'list_workspaces' and description 'List the workspace accessible with the current API key' indicate a retrieval operation that queries available workspaces without modification.
Attacks that exploit this kind of access
List the workspace accessible with the current API key. 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 list_workspaces: 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.
list_workspaces 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 list_workspaces 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 list_workspaces. 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.
list_workspaces is provided by the Roboflow MCP Server MCP server (nickedridge-wq/roboflow-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 →