Mark a task as completed.
AI agents use mark_as_completed to create or update resources in Trello Task Manager MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Trello Task Manager MCP environment.
The tool modifies the state of an existing task (marking it completed) but does not irreversibly delete or destroy data. It is not destructive because the action is reversible: a user or agent can mark the task as incomplete again. It is not read-only because it changes data.
From the tool's definition Tool name 'mark_as_completed' and description 'Mark a task as completed' indicate a state-modification operation on a task object. This is a reversible write operation—the task status can be changed back to incomplete if needed.
Attacks that exploit this kind of access
Mark a task as completed. It is categorised as a Write tool in the Trello Task Manager MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Trello Task Manager MCP server in PolicyLayer and add a rule for mark_as_completed: 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 Trello Task Manager MCP. Nothing to install.
mark_as_completed 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 mark_as_completed 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 mark_as_completed. 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.
mark_as_completed is provided by the Trello Task Manager MCP server (namuan/trello-task-manager-mcp). 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 →