add_employee
AI agents use add_employee to create or update resources in MCP Employee API Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Employee API Server environment.
The tool performs a create operation that adds new data to the employee database. This is reversible (records can be deleted), so it is Write rather than Destructive. The severity is medium because unauthorized employee record creation could cause operational issues, HR confusion, and potential compliance problems, but the blast radius is limited to employee data creation without financial impact.
From the tool's definition Tool name 'add_employee' combined with server description stating 'full CRUD operations' and 'create...employee records' indicates this tool creates new employee records.
Attacks that exploit this kind of access
add_employee. It is categorised as a Write tool in the MCP Employee API Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Employee API Server MCP server in PolicyLayer and add a rule for add_employee: 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 Employee API Server. Nothing to install.
add_employee 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 add_employee 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 add_employee. 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.
add_employee is provided by the MCP Employee API Server MCP server (josegarayar/mcp_test). 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 →