get_workspaces
AI agents call get_workspaces to retrieve information from PowerBI 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 metadata about PowerBI workspaces—a read-only operation with no side effects. While the description is empty, the naming convention and context of a query-oriented MCP server strongly indicate a simple GET operation. Confidence is slightly reduced due to the missing description, but the intent is clear from naming and server architecture.
From the tool's definition Tool name 'get_workspaces' indicates retrieval; server description emphasizes 'Query workspaces, datasets' as a read operation; sibling tools follow read patterns (get_*, query_dataset); no parameters or effects described suggest data retrieval only.
Attacks that exploit this kind of access
get_workspaces. It is categorised as a Read tool in the PowerBI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PowerBI MCP Server MCP server in PolicyLayer and add a rule for get_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 PowerBI MCP Server. Nothing to install.
get_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 get_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 get_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.
get_workspaces is provided by the PowerBI MCP Server MCP server (powerbi-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 →