Elimina una tarea por id y guarda el resultado en .xml.
AI agents call remove_task to permanently remove resources in Projectlibre — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes a task from a ProjectLibre project file and persists the change to disk (.xml/.pod format). Task deletion cannot be undone through the tool itself and modifies the underlying project structure irreversibly. This is a Destructive action rather than Write because it removes data rather than modifying it reversibly.
From the tool's definition Tool name 'remove_task' combined with description 'Elimina una tarea por id y guarda el resultado en .xml' (Spanish: 'Deletes a task by id and saves the result in .xml'). The verb 'elimina' (delete) indicates irreversible removal of data from a project file.
Attacks that exploit this kind of access
Elimina una tarea por id y guarda el resultado en .xml. It is categorised as a Destructive tool in the Projectlibre MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Projectlibre MCP server in PolicyLayer and add a rule for remove_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 Projectlibre. Nothing to install.
remove_task is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_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 remove_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.
remove_task is provided by the Projectlibre MCP server (osyanne/projectlibre-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 →