Update the text of a todo
AI agents use updateTodoText 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 modifies todo item text in a reversible manner (the previous text is not permanently lost and can typically be changed again). It does not delete data (which would be Destructive), execute arbitrary code (Execute), or affect financial systems. The low severity reflects the limited blast radius—a mistaken update affects only individual todo text entries, which can be corrected.
From the tool's definition Tool name 'updateTodoText' and description 'Update the text of a todo' indicate modification of existing data. The verb 'update' is characteristic of Write operations.
Attacks that exploit this kind of access
Update the text of a todo. 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 updateTodoText: 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.
updateTodoText 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 updateTodoText 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 updateTodoText. 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.
updateTodoText 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 →