Transition a milestone from 'planned' to 'in_progress'.
AI agents invoke ppm_milestone_start to trigger actions in Qod Ppm Odoo. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a workflow state transition rather than merely reading or writing data. State transitions in project management systems often trigger downstream effects—task scheduling, resource allocation, timeline updates, and notifications—whose consequences depend on the project context.
From the tool's definition Tool performs a state transition ('planned' to 'in_progress') on a milestone, which triggers workflow actions and updates project status in Odoo.
Attacks that exploit this kind of access
Transition a milestone from 'planned' to 'in_progress'. It is categorised as a Execute tool in the Qod Ppm Odoo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Qod Ppm Odoo MCP server in PolicyLayer and add a rule for ppm_milestone_start: 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_start is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ppm_milestone_start 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_start. 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_start 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 →