This record as markdown: /tools/funny-booth-aos-mcp-server/complete-todo.md
What complete_todo does on Aos
AI agents use complete_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 |
|---|---|---|---|
id | string | Yes | ToDoID |
Parameters from the server's own tool schema.
Why complete_todo is rated Medium
Completing a to-do is a reversible modification operation (can typically be undone by reverting status), so it fits Write rather than Destructive or Execute. Severity is medium because misuse could create data inconsistency (marking incomplete work as done), but the impact is generally limited to task metadata without broader system effects.
From the tool's definition Tool name 'complete_todo' indicates marking a to-do item as complete, which modifies the state of data. Sibling tools on the server include 'create_todo', 'create_task', 'delete_backlog_item', and other CRUD operations, suggesting this is part of a…
Attacks that exploit this kind of access
The rule that runs complete_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 complete_todo, this is the rule to start with:
complete_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 complete_todo call is checked against it from then on.
Questions about complete_todo
complete_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.
complete_todo accepts 1 parameter: id. Required: 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 complete_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.
complete_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 complete_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 complete_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.
complete_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