workspace_current

Return the workspace this MCP API key is currently routed to, with the caller's role inside it. Use this to confirm context before/after workspace.switch.

SERVERDialogbrain SOURCEhttps://api.dialogbrain.com/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-saloprj-dialogbrain/workspace-current.md

WHAT IT DOES

What workspace_current does on Dialogbrain

AI agents call workspace_current to retrieve information from Dialogbrain without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why workspace_current is rated Low

This tool only retrieves and returns information about the current workspace and caller role. It has no side effects, does not modify any data, and is purely a read/query operation used for context confirmation.

From the tool's definition Return the workspace this MCP API key is currently routed to, with the caller's role inside it

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs workspace_current safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For workspace_current, this is the rule to start with:

workspace_current Allowed

workspace_current is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "workspace_current": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every workspace_current call is checked against it from then on.

FAQ

Questions about workspace_current

What does the workspace_current tool do? +

Return the workspace this MCP API key is currently routed to, with the caller's role inside it. Use this to confirm context before/after workspace.switch. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on workspace_current? +

Register the Dialogbrain MCP server in PolicyLayer and add a rule for workspace_current: 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 Dialogbrain. Nothing to install.

What risk level is workspace_current? +

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

Can I rate-limit workspace_current? +

Yes. Add a rate_limit block to the workspace_current 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 workspace_current completely? +

Set action: deny in the PolicyLayer policy for workspace_current. 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 workspace_current? +

workspace_current is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Dialogbrain, and thousands of servers like it.

This server

All 225 Dialogbrain tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →