AI agents call odoo_find_attendance 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.
Based on naming conventions in the sibling tools (check_in, check_out, approve_expense) and the 'find' prefix, this tool most likely retrieves or searches attendance data from Odoo's HR/attendance module. No side effects or data modification is implied by the name. The empty description prevents higher confidence, but the predominant pattern across MCP tools suggests 'find' operations are Read-category retrievals.
From the tool's definition Tool name 'odoo_find_attendance' indicates a query/lookup operation for attendance records. The 'find' verb typically denotes retrieval without modification. Description is empty, reducing confidence slightly.
Attacks that exploit this kind of access
odoo_find_attendance. 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_find_attendance: 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_find_attendance 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_find_attendance 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_find_attendance. 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_find_attendance 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 →