Mark a task as complete
AI agents use tududi_complete_task to create or update resources in Tududi MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tududi MCP environment.
Completing a task updates the task's status field reversibly (tasks can be marked incomplete again), making this a Write action rather than Destructive. The operation has limited blast radius since it affects only metadata state of a single task, not deletion or financial consequences. Confidence is high because the intent is unambiguous from the name and description.
From the tool's definition Tool name 'tududi_complete_task' and description 'Mark a task as complete' indicate a state modification operation on a task object.
Attacks that exploit this kind of access
Mark a task as complete. It is categorised as a Write tool in the Tududi MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tududi MCP server in PolicyLayer and add a rule for tududi_complete_task: 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 Tududi MCP. Nothing to install.
tududi_complete_task 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 tududi_complete_task 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 tududi_complete_task. 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.
tududi_complete_task is provided by the Tududi MCP server (jerrytunin/tududi-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 →