Move an issue from 'new' to 'assigned'.
AI agents use ppm_issue_assign 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 changes the state of an issue by transitioning it from one status to another. State transitions are Write operations—they modify data (the issue record and its status field) but are reversible (the issue can be moved back or reassigned). The modification affects issue tracking records but does not delete data, execute arbitrary code, or trigger financial transactions.
From the tool's definition 'Move an issue from 'new' to 'assigned'' describes a state transition that modifies issue status, which is a reversible data modification operation.
Attacks that exploit this kind of access
Move an issue from 'new' to 'assigned'. 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_issue_assign: 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_issue_assign 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_issue_assign 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_issue_assign. 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_issue_assign 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 →