getWorkspace
Read a single workspace by id. Auth via the standard workspace-access ladder (credential org match + workspace scope + per-resource read permission). Returns the full v_workspaces row. Read-only.
This record as markdown: /tools/io-stablebaseline-sb/getworkspace.md
What getWorkspace does on Stable Baseline
AI agents call getWorkspace to retrieve information from Stable Baseline without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
workspace_id | string | Yes | Workspace UUID. |
Parameters from the server's own tool schema.
Why getWorkspace is rated Low
This tool retrieves workspace metadata with no side effects. The description confirms read-only semantics and access is controlled by standard permission checks (workspace-access ladder, credential matching, scope validation, per-resource read permission). The blast radius if misused is limited to information disclosure of workspace details only.
From the tool's definition Tool name 'getWorkspace' and description explicitly states 'Read a single workspace by id' and 'Read-only.' Returns workspace data without modification.
Attacks that exploit this kind of access
The rule that runs getWorkspace safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stable Baseline, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getWorkspace, this is the rule to start with:
getWorkspace is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every getWorkspace call is checked against it from then on.
Questions about getWorkspace
Read a single workspace by id. Auth via the standard workspace-access ladder (credential org match + workspace scope + per-resource read permission). Returns the full v_workspaces row. Read-only. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
getWorkspace accepts 1 parameter: workspace_id. Required: workspace_id. The full parameter table on this page comes from the server's own tool schema.
Register the Stable Baseline MCP server in PolicyLayer and add a rule for getWorkspace: 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 Stable Baseline. Nothing to install.
getWorkspace 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 getWorkspace 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 getWorkspace. 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.
getWorkspace is provided by the Stable Baseline MCP server (https://api.stablebaseline.io/functions/v1/cloud-serve/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stable Baseline, and thousands of servers like it.
This server
Across the catalogue