update_workspace · Sidvy MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_workspace does on Sidvy MCP Server

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

WHY IT NEEDS A POLICY

Why update_workspace needs a policy

This tool modifies workspace configuration (specifically the name) reversibly. It does not delete data (not Destructive), execute arbitrary code (not Execute), involve financial transactions (not Financial), or merely retrieve data (not Read). Update operations that change workspace properties are Write-category operations.

From the tool's definition Tool name 'update_workspace' and description 'Update a workspace (currently only name changes supported)' indicate modification of existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_workspace Rate-limited

update_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": {
    "update_workspace": {
      "limits": [
        {
          "counter": "update_workspace_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Sidvy MCP Server, so you can run agents against it safely.

FAQ

Questions about update_workspace

What does the update_workspace tool do? +

Update a workspace (currently only name changes supported). It is categorised as a Write tool in the Sidvy 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 update_workspace? +

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

What risk level is update_workspace? +

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

Can I rate-limit update_workspace? +

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

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

update_workspace is provided by the Sidvy MCP Server MCP server (martinhjartmyr/sidvy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.