Delete an LDAP entry by distinguished name.
AI agents call delete_entry to permanently remove resources in Ldap — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible delete operation on LDAP directory entries. Deletion of directory entries (users, groups, resources) is a destructive action that cannot be undone through the tool itself. An AI agent with access to this tool could maliciously or accidentally remove critical identity and access management data, organizational structures, or service accounts, causing significant operational impact.
From the tool's definition Tool name 'delete_entry' combined with description 'Delete an LDAP entry by distinguished name' indicates irreversible deletion of directory data. LDAP entries once deleted cannot be recovered without restoration from backups.
Attacks that exploit this kind of access
Delete an LDAP entry by distinguished name. It is categorised as a Destructive tool in the Ldap MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ldap MCP server in PolicyLayer and add a rule for delete_entry: 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 Ldap. Nothing to install.
delete_entry is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_entry 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 delete_entry. 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.
delete_entry is provided by the Ldap MCP server (markizano/ldap-mcp-server). 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 →