Mark a todo as completed
AI agents use complete_todo to create or update resources in MCP Personal Assistant — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Personal Assistant environment.
This tool modifies data reversibly—a completed todo can be marked incomplete again. It is not destructive (data is preserved), not execute (no arbitrary code/commands), and not financial. The modification is localized to a single todo item with minimal blast radius if misused by an AI agent. Classified as Write with low severity.
From the tool's definition Tool name 'complete_todo' and description 'Mark a todo as completed' indicate a state modification operation that updates an existing record (from incomplete to complete status) without deleting or destroying data.
Attacks that exploit this kind of access
Mark a todo as completed. It is categorised as a Write tool in the MCP Personal Assistant MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Personal Assistant 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 MCP Personal Assistant. 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 MCP Personal Assistant MCP server (swapnilsurdi/mcp-pa). 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 →