get_workspace
Get one workspace by id or slug.
This record as markdown: /tools/dev-busymate-busymate-devtools/get-workspace.md
What get_workspace does on Busymate DevTools
AI agents call get_workspace to retrieve information from Busymate DevTools 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 |
|---|---|---|---|
id | string | — | |
slug | string | — |
Parameters from the server's own tool schema.
Why get_workspace is rated Low
This tool retrieves workspace metadata by identifier. It is a simple query operation that returns data without side effects, making it a Read category tool. Severity is low because reading workspace information presents minimal risk—no data is modified, deleted, or used to trigger external actions. The tool's purpose is information retrieval only.
From the tool's definition Tool name 'get_workspace' and description 'Get one workspace by id or slug' indicate a retrieval operation with no modification or execution.
Attacks that exploit this kind of access
The rule that runs get_workspace safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Busymate DevTools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_workspace, this is the rule to start with:
get_workspace 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 Busymate DevTools, apply this rule, and every get_workspace call is checked against it from then on.
Questions about get_workspace
Get one workspace by id or slug. It is categorised as a Read tool in the Busymate DevTools MCP Server, which means it retrieves data without modifying state.
get_workspace accepts 2 parameters: id, slug. The full parameter table on this page comes from the server's own tool schema.
Register the Busymate DevTools MCP server in PolicyLayer and add a rule for get_workspace: 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 Busymate DevTools. Nothing to install.
get_workspace 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_workspace 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_workspace. 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_workspace is provided by the Busymate DevTools MCP server (https://mcp.busymate.dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Busymate DevTools, and thousands of servers like it.
This server
Across the catalogue