Add a new TODO item to the list. Provide a text for the task you want to add. Returns a confirmation message with the new TODO id.
AI agents use addTodo to create or update resources in Remote MCP with Azure Container Apps — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Remote MCP with Azure Container Apps environment.
This tool creates a new TODO item reversibly. It modifies state by adding data but does not execute arbitrary code, delete data, or cause financial impact. The sibling tools (completeTodo, deleteTodo, listTodos, updateTodoText) confirm this is a task management system where addTodo is a standard write operation.
From the tool's definition Tool description states 'Add a new TODO item to the list' and 'Returns a confirmation message with the new TODO id', indicating creation of a new data entry.
Attacks that exploit this kind of access
Add a new TODO item to the list. Provide a text for the task you want to add. Returns a confirmation message with the new TODO id. It is categorised as a Write tool in the Remote MCP with Azure Container Apps MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Remote MCP with Azure Container Apps MCP server in PolicyLayer and add a rule for addTodo: 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 Remote MCP with Azure Container Apps. Nothing to install.
addTodo 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 addTodo 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 addTodo. 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.
addTodo is provided by the Remote MCP with Azure Container Apps MCP server (powerstar13/copilot-mcp-poc). 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 →