Create a new todo for the user. Set alarm_at to an ISO 8601 formatted date-time string if the todo has a specific deadline or reminder time.
AI agents use create-todo to create or update resources in BeeMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BeeMCP environment.
The tool creates a new todo item, which is a write operation that adds data to the user's todo list. This is reversible (todos can be deleted, as evidenced by the sibling tool 'delete-todo'). The operation has minimal blast radius—a misused todo creation would simply add unwanted items that can be removed. There is no financial impact, no irreversible deletion, and no code execution.
From the tool's definition Tool description states 'Create a new todo for the user', which is a create operation that modifies user data reversibly.
Documented attack patterns abuse exactly the kind of access create-todo gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BeeMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create-todo:
{
"version": "1",
"default": "deny",
"tools": {
"create-todo": {
"limits": [
{
"counter": "create-todo_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Create a new todo for the user. Set alarm_at to an ISO 8601 formatted date-time string if the todo has a specific deadline or reminder time. It is categorised as a Write tool in the BeeMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bee 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 BeeMCP. Nothing to install.
create-todo 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-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.
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.
create-todo is provided by the Bee MCP server (okgodoit/beemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 BeeMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
19 BeeMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.