// SCAN REPORT

Sidvy MCP Server

48 tools. 25 can modify or destroy data without limits.

4 destructive tools with no built-in limits. Policy required.

Last updated: 4 Jul 2026

25 can modify or destroy data

23 read-only

48 tools total

Community server · catalogue entry verified 04/07/2026

How to control Sidvy MCP Server ↓

TOOL MAP

What Sidvy MCP Server exposes to your agents

Read (23) Write / Execute (21) Destructive / Financial (4)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Sidvy MCP Server tools

Destructive · High delete_group This tool irreversibly deletes data (groups and their children) and cannot be undone. Destructive · High delete_note This tool removes data irreversibly from a user's active notes. Destructive · Medium delete_todo The tool irreversibly removes a todo item from the user's workspace. Destructive · High delete_workspace This tool irreversibly deletes an entire workspace and all associated data.

25 of Sidvy MCP Server's 48 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Sidvy MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Sidvy MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_group": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "append_to_daily_note": {
    "limits": [
      {
        "counter": "append_to_daily_note_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "can_create_workspace": {
    "limits": [
      {
        "counter": "can_create_workspace_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Sidvy MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON SIDVY →

Instant setup, no code required.

FULL CATALOGUE

All 48 Sidvy MCP Server tools

DESTRUCTIVE 4 tools

Destructive delete_group Delete a group and all its child groups (cascade delete) Destructive delete_note Delete a note (moves to trash) Destructive delete_todo Delete a todo (soft delete) Destructive delete_workspace Delete a workspace and all its content (cannot delete default workspace)

WRITE 21 tools

Write append_to_daily_note Append content to today Write append_to_note Append content to an existing note Write append_to_weekly_note Append content to the current week Write complete_todo Mark a todo as completed Write create_group Create a new group for organizing notes Write create_group_path Create a nested group structure from a path (creates missing parent groups) Write create_note Create a new note with markdown content Write create_todo Create a new todo associated with a note Write create_todos_for_note Create multiple todos for a note at once Write create_workspace Create a new workspace (max 2 workspaces per user) Write move_group Move a group to a new parent (or to root level) Write rename_workspace Rename an existing workspace Write switch_workspace Switch context to a different workspace (for subsequent operations) Write toggle_todo Toggle a todo Write uncomplete_todo Mark a todo as incomplete Write update_daily_note Update the content of today Write update_group Update a group Write update_note Update an existing note Write update_todo Update a todo Write update_weekly_note Update the content of the current week Write update_workspace Update a workspace (currently only name changes supported)

READ 23 tools

Read can_create_workspace Check if the user can create another workspace (max 2 allowed) Read get_child_groups Get all child groups of a specific parent group Read get_completed_todos Get all completed todos Read get_daily_note Get today Read get_default_workspace Get the user Read get_group_path Get the full path from root to a specific group Read get_group_tree Get the hierarchical tree structure of all groups in a workspace Read get_note Get a specific note by ID Read get_pending_todos Get all incomplete/pending todos Read get_recent_notes Get recently updated notes Read get_root_groups Get all root-level groups (groups with no parent) Read get_todo_stats Get statistics about todos (total, completed, pending, completion rate) Read get_todos_for_note Get all todos associated with a specific note Read get_weekly_note Get the current week Read get_workspace Get details of a specific workspace Read get_workspace_by_name Find a workspace by its name Read get_workspace_stats Get detailed statistics for a workspace Read list_groups List groups with hierarchical structure and filtering Read list_notes List notes with optional filtering and search capabilities Read list_todos List todos with filtering options (by completion status, note, etc.) Read list_workspaces List all workspaces for the authenticated user with content counts Read search_notes Search notes by content or title with full-text search Read search_todos Search todos by text content

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Sidvy MCP Server

Can an AI agent delete data through the Sidvy MCP Server MCP server? +

Yes. The Sidvy MCP Server server exposes 4 destructive tools including delete_group, delete_note, delete_todo. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Sidvy MCP Server? +

The Sidvy MCP Server server has 21 write tools including append_to_daily_note, append_to_note, append_to_weekly_note. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Sidvy MCP Server.

How many tools does the Sidvy MCP Server MCP server expose? +

48 tools across 3 categories: Destructive, Read, Write. 23 are read-only. 25 can modify, create, or delete data.

How do I enforce a policy on Sidvy MCP Server? +

Register the Sidvy MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Sidvy MCP Server tool call.

Deterministic rules across all 48 Sidvy MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON SIDVY →

Instant setup, no code required.

48 Sidvy MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.