Create multiple todos for a note at once
AI agents use create_todos_for_note 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.
This tool creates new todo items, which are reversible modifications to the workspace state. It falls under Write category as it creates data without permanent destruction. Severity is medium because mass creation of todos could clutter a workspace or consume resources, but the effect is reversible through standard deletion operations.
From the tool's definition Tool name 'create_todos_for_note' and description 'Create multiple todos for a note at once' indicate creation of new data entities (todos) within the note-taking system.
Attacks that exploit this kind of access
Create multiple todos for a note at once. 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.
Register the Sidvy MCP Server MCP server in PolicyLayer and add a rule for create_todos_for_note: 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.
create_todos_for_note is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_todos_for_note 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.
Set action: deny in the PolicyLayer policy for create_todos_for_note. 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.
create_todos_for_note 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →