Transition a risk from 'identified' to 'analyzing'.
AI agents invoke ppm_risk_start_analysis 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 state machine transition with side effects that modify risk workflow status. While not destructive (the change is reversible via other transitions like ppm_risk_* reset operations) and not a simple write (it invokes specialized workflow logic beyond CRUD), it qualifies as Execute because it triggers Odoo workflow actions whose downstream consequences depend on system state.
From the tool's definition Tool performs a state transition ('identified' to 'analyzing') on a risk object, which triggers workflow logic and potentially downstream operations in the Odoo PPM system.
Attacks that exploit this kind of access
Transition a risk from 'identified' to 'analyzing'. 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_risk_start_analysis: 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_risk_start_analysis 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_risk_start_analysis 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_risk_start_analysis. 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_risk_start_analysis 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 →