Add a new LDAP entry
AI agents use ldap_add to create or update resources in Mcp Database — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Database environment.
This tool creates new entries in LDAP directories, which are critical infrastructure for identity and access management. While reversible (entries can be deleted), adding LDAP entries modifies authentication systems and could grant unauthorized access or disrupt directory integrity. The blast radius is high because malicious LDAP entries could affect authentication across many systems.
From the tool's definition Tool name 'ldap_add' and description 'Add a new LDAP entry' indicate creation of new directory entries in LDAP systems, which are typically used for authentication and authorization management.
Attacks that exploit this kind of access
Add a new LDAP entry. It is categorised as a Write tool in the Mcp Database MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Database MCP server in PolicyLayer and add a rule for ldap_add: 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 Database. Nothing to install.
ldap_add 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 ldap_add 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 ldap_add. 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.
ldap_add is provided by the Mcp Database MCP server (nam088/mcp-database-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 →