check_ldap

Check LDAP server connectivity and verify it speaks the LDAP protocol. Sends an anonymous LDAPv3 bind request and checks for a valid response. port: 389 (LDAP), 636 (LDAPS). use_ssl: connect with TLS (default False; automatically True for port 636). Does not authenticate — anonymous bind only.

SERVERMcp Nettools SOURCEaaronckj/mcp-nettools

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aaronckj-mcp-nettools/check-ldap.md

WHAT IT DOES

What check_ldap does on Mcp Nettools

AI agents call check_ldap to retrieve information from Mcp Nettools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why check_ldap is rated Low

This is a network diagnostic tool that queries LDAP server status through a read-only anonymous bind. It retrieves no sensitive data and causes no side effects. Anonymous LDAP queries are standard diagnostic operations with minimal security impact, though the tool does probe network infrastructure which warrants a 'low' severity rating rather than being entirely benign.

From the tool's definition The tool performs an anonymous LDAP bind request to check server connectivity and protocol compliance. It explicitly states 'Does not authenticate — anonymous bind only' and only verifies responses without modifying, executing, or deleting any data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_ldap safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Nettools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_ldap, this is the rule to start with:

check_ldap Allowed

check_ldap is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_ldap": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Nettools, apply this rule, and every check_ldap call is checked against it from then on.

FAQ

Questions about check_ldap

What does the check_ldap tool do? +

How do I enforce a policy on check_ldap? +

Register the Mcp Nettools MCP server in PolicyLayer and add a rule for check_ldap: 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 Nettools. Nothing to install.

What risk level is check_ldap? +

check_ldap is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_ldap? +

Yes. Add a rate_limit block to the check_ldap 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.

How do I block check_ldap completely? +

Set action: deny in the PolicyLayer policy for check_ldap. 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.

What MCP server provides check_ldap? +

check_ldap is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Nettools, and thousands of servers like it.

This server

All 235 Mcp Nettools tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →