AI agents call odoo_list_pending_activities to retrieve information from Odooclaw without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Listing pending activities is a data retrieval operation that queries existing records without modifying, deleting, or executing external actions. Despite the empty description reducing confidence slightly, the 'list' verb is a clear indicator of a Read-category tool. The low severity reflects minimal blast radius—an agent mistakenly listing activities causes no harm.
From the tool's definition Tool name 'odoo_list_pending_activities' uses the verb 'list', which indicates querying/retrieval. The description is empty, limiting specificity, but 'list' operations are by definition Read operations with no side effects.
Attacks that exploit this kind of access
odoo_list_pending_activities. It is categorised as a Read tool in the Odooclaw MCP Server, which means it retrieves data without modifying state.
Register the Odooclaw MCP server in PolicyLayer and add a rule for odoo_list_pending_activities: 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 Odooclaw. Nothing to install.
odoo_list_pending_activities 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 odoo_list_pending_activities 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 odoo_list_pending_activities. 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.
odoo_list_pending_activities is provided by the Odooclaw MCP server (nicolasramos/odooclaw-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 →