criar_funcionario
AI agents use criar_funcionario to create or update resources in MCP Officegest — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Officegest environment.
This tool creates a new employee record in the Officegest system, which is a reversible write operation. It modifies data but does not irreversibly delete it. Severity is medium because employee creation could affect payroll, access controls, or organizational structure if misused by an AI agent, though the impact is localized to HR/personnel data rather than financial transactions or destructive operations.
From the tool's definition Tool name 'criar_funcionario' translates to 'create_employee' in Portuguese, indicating creation of a new employee record.
Attacks that exploit this kind of access
criar_funcionario. It is categorised as a Write tool in the MCP Officegest MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Officegest MCP server in PolicyLayer and add a rule for criar_funcionario: 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 MCP Officegest. Nothing to install.
criar_funcionario 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 criar_funcionario 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 criar_funcionario. 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.
criar_funcionario is provided by the MCP Officegest MCP server (rubencodex86/officegest-api-v2-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 →