Mark a risk as occurred.
AI agents use ppm_risk_mark_occurred 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.
This tool modifies the state of a risk entity in the Odoo PPM system. It is reversible (the risk status can presumably be changed back via other tools like state transitions), so it falls under Write rather than Destructive.
From the tool's definition Tool name is 'ppm_risk_mark_occurred' and description states 'Mark a risk as occurred.' This updates the state of an existing risk record from unoccurred to occurred status.
Attacks that exploit this kind of access
Mark a risk as occurred. 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_mark_occurred: 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_mark_occurred 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_mark_occurred 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_mark_occurred. 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_mark_occurred 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 →