Skip to main content
Glama

certipy_scan

Scan Active Directory Certificate Services to identify AD CS vulnerabilities for security assessment and penetration testing.

Instructions

Call this to enumerating Active Directory Certificate Services (AD CS) vulnerabilities. username syntax is: username@domain

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYes
usernameYes
passwordYes
ntlmNo
kerberosNo

Implementation Reference

  • The handler function for the 'certipy_scan' tool. It is registered via the @mcp.tool decorator and executes the 'certipy find' command with options based on authentication method (NTLM or Kerberos) to scan for Active Directory Certificate Services vulnerabilities.
    @mcp.tool(name="certipy_scan",description="Call this to enumerating Active Directory Certificate Services (AD CS) vulnerabilities. username syntax is: username@domain")
    def certipy_scan(ip:str,username:str,password:str,ntlm:bool=False,kerberos:bool=False):
        if ntlm:
            return run_command(["certipy","find","-vulnerable","-u", user ,"-hashes",password,"-dc-ip",ip,"-stdout"])
        if kerberos:
            return run_command(["certipy","find","-vulnerable","-u", user ,"-k","-p",password,"-dc-ip",ip,"-stdout"])
    
        return run_command(["certipy","find","-vulnerable","-u", user ,"-p",password,"-dc-ip",ip,"-stdout"])
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It only mentions username syntax and implies vulnerability scanning, but lacks details on authentication methods (e.g., NTLM/Kerberos flags), rate limits, output format, or potential impacts. This is inadequate for a tool with 5 parameters and security implications.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief and front-loaded with the main purpose, but the second sentence about username syntax feels tacked on without integrating into a cohesive structure. It's concise but could be more smoothly organized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (5 parameters, security tool, no annotations, no output schema), the description is incomplete. It doesn't cover parameter meanings, behavioral traits, or output expectations, making it insufficient for safe and effective use by an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It only explains username syntax, leaving ip, password, ntlm, and kerberos parameters without semantic context. This fails to add meaningful meaning beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose as 'enumerating Active Directory Certificate Services (AD CS) vulnerabilities,' which is a specific verb+resource combination. However, it doesn't explicitly differentiate this from sibling tools like 'check_module' or 'run_nmap_scan' that might also perform security assessments, so it misses full sibling distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It mentions username syntax but doesn't specify contexts, prerequisites, or exclusions, leaving the agent with no usage direction beyond the basic purpose.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/YoussefSahnoun/PentestMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server