current_workspace

Return the Sanka workspace currently bound to this MCP session, including workspace_name, workspace_code, and internal workspace_id. Use this to verify workspace context before live Sanka operations.

SERVERSanka MCP Server SOURCEsankahq/sanka-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sankahq-sanka-mcp/current-workspace.md

WHAT IT DOES

What current_workspace does on Sanka MCP Server

AI agents use current_workspace to create or update resources in Sanka MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sanka MCP Server environment.

RISK

Why current_workspace is rated Medium

An AI agent can call current_workspace faster than any human can review: one bad instruction and it creates or modifies resources in Sanka MCP Server by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs current_workspace safely

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

current_workspace Rate-limited

current_workspace stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "current_workspace": {
      "limits": [
        {
          "counter": "current_workspace_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about current_workspace

What does the current_workspace tool do? +

Return the Sanka workspace currently bound to this MCP session, including workspace_name, workspace_code, and internal workspace_id. Use this to verify workspace context before live Sanka operations. It is categorised as a Write tool in the Sanka MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on current_workspace? +

Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for current_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 Sanka MCP Server. Nothing to install.

What risk level is current_workspace? +

current_workspace is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit current_workspace? +

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

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

current_workspace is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sanka MCP Server, and thousands of servers like it.

This server

All 349 Sanka MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →