move_group · Sidvy MCP Server MCP: Risk & Policy

WHAT IT DOES

What move_group does on Sidvy MCP Server

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

The tool modifies data (group hierarchy/location) but does not delete, execute code, move money, or perform irreversible operations. Moving a group to a different parent is a reversible write operation. Severity is medium because misuse could disorganize user workspace structure, but the change is non-destructive and can be undone by moving the group again.

From the tool's definition Tool description: "Move a group to a new parent (or to root level)" - this modifies the hierarchical structure of a group by changing its parent, which is a reversible structural change to the note-taking workspace.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_group Rate-limited

move_group 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": {
    "move_group": {
      "limits": [
        {
          "counter": "move_group_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 move_group

What does the move_group tool do? +

Move a group to a new parent (or to root level). 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 move_group? +

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

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

Can I rate-limit move_group? +

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

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

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