Start review of a submitted Change Request.
AI agents invoke ppm_change_request_start_review 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 non-trivial workflow action (state transition) rather than simply reading or writing data. It triggers external workflow logic in Odoo that cannot be easily undone and affects downstream processes. While not immediately destructive, it commits a change request to a review state with business process implications.
From the tool's definition Tool name 'ppm_change_request_start_review' and description 'Start review of a submitted Change Request' indicate triggering a workflow state transition action.
Attacks that exploit this kind of access
Start review of a submitted Change Request. 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_change_request_start_review: 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_change_request_start_review 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_change_request_start_review 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_change_request_start_review. 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_change_request_start_review 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 →