Cancel a milestone.
AI agents call ppm_milestone_cancel to permanently remove resources in Qod Ppm Odoo — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling a milestone in a project management context is a destructive state transition: it removes the milestone from active workflows and likely cannot be trivially reversed. While it may not delete data outright, cancellation in PPM systems is generally a terminal or near-terminal state that significantly impacts project planning and reporting.
From the tool's definition 'Cancel a milestone' — cancelling a milestone is a state transition that is typically irreversible or difficult to undo, removing it from active project tracking.
Attacks that exploit this kind of access
Cancel a milestone. It is categorised as a Destructive tool in the Qod Ppm Odoo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Qod Ppm Odoo MCP server in PolicyLayer and add a rule for ppm_milestone_cancel: 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 Qod Ppm Odoo. Nothing to install.
ppm_milestone_cancel 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 ppm_milestone_cancel 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 ppm_milestone_cancel. 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.
ppm_milestone_cancel is provided by the Qod Ppm Odoo MCP server (wethti/qod-ppm-odoo-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 →