Move a risk in the P×I matrix.
AI agents use ppm_risk_move_in_matrix to create or update resources in Qod Ppm Odoo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Qod Ppm Odoo environment.
The tool moves (repositions) a risk within a Probability×Impact matrix, which constitutes modifying existing risk management data. This is a Write operation because it updates risk attributes reversibly (the risk can be moved again to correct position). It is not Destructive because the risk record is not deleted.
From the tool's definition Tool description states "Move a risk in the P×I matrix" - this modifies risk positioning/data within a project risk management matrix, which is a reversible update operation.
Attacks that exploit this kind of access
Move a risk in the P×I matrix. It is categorised as a Write tool in the Qod Ppm Odoo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Qod Ppm Odoo MCP server in PolicyLayer and add a rule for ppm_risk_move_in_matrix: 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_move_in_matrix is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ppm_risk_move_in_matrix 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_move_in_matrix. 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_move_in_matrix 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 →