This record as markdown: /tools/funny-booth-aos-mcp-server/create-todo.md
What create_todo does on Aos
AI agents use create_todo to create or update resources in Aos, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aos environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
title | string | Yes | ToDo名 |
team_id | string | — | 対象チームID（省略時はユーザーの既定チーム） |
owner_id | string | Yes | 担当メンバーID |
meeting_date | string | — | 会議日 YYYY-MM-DD（期日は +7日で自動設定） |
Parameters from the server's own tool schema.
Why create_todo is rated Medium
This tool creates a new TODO entry, which is a reversible write operation that modifies data state but does not delete or execute external code. Severity is medium because uncontrolled TODO creation could clutter systems, but individual TODOs are low-consequence items. Confidence is slightly reduced due to lack of explicit description, but the name and sibling context strongly indicate a write operation.
From the tool's definition Tool name 'create_todo' indicates creation of a TODO item. Sibling tools include 'complete_task', 'complete_todo', 'create_task', 'delete_backlog_item', and other write/destructive operations, confirming this server manages task/project data.
Attacks that exploit this kind of access
The rule that runs create_todo safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_todo, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every create_todo call is checked against it from then on.
Questions about create_todo
create_todo is a write tool on the Aos MCP server. It is categorised as a Write tool in the Aos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_todo accepts 4 parameters: title, team_id, owner_id, meeting_date. Required: title, owner_id. The full parameter table on this page comes from the server's own tool schema.
Register the Aos 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 Aos. 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 Aos MCP server (@funny-booth/aos-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aos, and thousands of servers like it.
This server
Across the catalogue