Low Risk

get_workspace

Get the current Docmost workspace

How to control get_workspace ↓

What get_workspace does on Docmost MCP Server

AI agents call get_workspace to retrieve information from Docmost MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_workspace needs a policy

This tool retrieves metadata about the current workspace without creating, modifying, or deleting any data. It is a read-only query operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'get_workspace' and description 'Get the current Docmost workspace' indicate a retrieval operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access get_workspace gives an agent:

How to control get_workspace

PolicyLayer is an MCP gateway — it sits between your AI agents and Docmost MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_workspace:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_workspace": {}
  }
}

get_workspace is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Docmost MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_workspace

What does the get_workspace tool do? +

Get the current Docmost workspace. It is categorised as a Read tool in the Docmost MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_workspace? +

Register the Docmost MCP Server 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 Docmost MCP Server. Nothing to install.

What risk level is get_workspace? +

get_workspace is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_workspace? +

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.

How do I block get_workspace completely? +

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.

What MCP server provides get_workspace? +

get_workspace is provided by the Docmost MCP Server MCP server (mrmartinimo/docmost-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Docmost MCP Server tool call.

Start from Docmost MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

11 Docmost MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.