rename_workspace · Sidvy MCP Server MCP: Risk & Policy

WHAT IT DOES

What rename_workspace does on Sidvy MCP Server

AI agents use rename_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 rename_workspace needs a policy

Renaming a workspace modifies metadata but does not delete or irreversibly destroy data, nor does it execute arbitrary code or move money. It is a reversible write operation. Severity is medium because renaming a workspace could cause confusion or break integrations if an AI agent renames critical workspaces without proper context, but the change is easily undone.

From the tool's definition Tool name 'rename_workspace' and description 'Rename an existing workspace' indicate modification of existing data. The action is reversible—workspaces can be renamed again to restore prior names.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_workspace Rate-limited

rename_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": {
    "rename_workspace": {
      "limits": [
        {
          "counter": "rename_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 rename_workspace

What does the rename_workspace tool do? +

Rename an existing workspace. 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 rename_workspace? +

Register the Sidvy MCP Server MCP server in PolicyLayer and add a rule for rename_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 rename_workspace? +

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

Can I rate-limit rename_workspace? +

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

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

rename_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.