Export the risk register to XLSX.
AI agents call ppm_export_risks to retrieve information from Qod Ppm Odoo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Exporting data to a file format (XLSX) is a read/retrieval operation — it queries the risk register and produces a downloadable report. No data is created, modified, or deleted. Misuse has minimal blast radius.
From the tool's definition Export the risk register to XLSX
Attacks that exploit this kind of access
Export the risk register to XLSX. It is categorised as a Read tool in the Qod Ppm Odoo MCP Server, which means it retrieves data without modifying state.
Register the Qod Ppm Odoo MCP server in PolicyLayer and add a rule for ppm_export_risks: 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_export_risks is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ppm_export_risks 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_export_risks. 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_export_risks 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 →