create_todo · Sidvy MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_todo does on Sidvy MCP Server

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

This tool creates new todo items, which modifies the workspace state reversibly. It does not execute arbitrary code, delete data irreversibly, or move money. While creating todos can have downstream workflow implications, the action itself is a standard write operation. Severity is medium because unintended todo creation at scale could clutter a workspace, but the impact is bounded and reversible through deletion.

From the tool's definition Tool name 'create_todo' and description 'Create a new todo associated with a note' indicate data creation. The sibling tools show this server manages notes, todos, groups, and workspaces—all reversible operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_todo Rate-limited

create_todo 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": {
    "create_todo": {
      "limits": [
        {
          "counter": "create_todo_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 create_todo

What does the create_todo tool do? +

Create a new todo associated with a note. 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 create_todo? +

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

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

Can I rate-limit create_todo? +

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

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

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