Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

security_password_policy_generator

Read-onlyIdempotent

Generate a password policy document and validators (regex, JSON Schema, etc.) from your complexity constraints. Includes built-in compliance baselines such as NIST 800-63B and PCI DSS 4.0.

Instructions

Password Policy Document and Validator Generator. Generate a written corporate password policy (Markdown plus rendered HTML) together with machine-readable validators (regex, JSON Schema, nginx, htpasswd, Active Directory, k8s, JavaScript, Python) from declared complexity constraints. Set operation to generate with an input object of constraints, or operation presets to list 8 built-in compliance baselines (NIST 800-63B, PCI DSS 4.0, HIPAA, ISO 27001, OWASP ASVS, Microsoft Entra, Google Workspace) you can use as a starting input. Use security_password_policy_generator to author the rules a workforce must follow; use crypto_password_generator instead to produce actual random passwords, or crypto_password_strength to score one password. Deterministic from its inputs (same input gives same document), pure compute: read-only, non-destructive, contacts no external service, no randomness, and rate-limited (30 requests/minute for anonymous callers). Returns the policy markdown and html, a validator regex, a JSON Sch

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYesgenerate builds a policy from the input object; presets ignores input and returns the 8 built-in compliance baselines.generate
inputNoPolicy constraints (required when operation is generate; ignored for presets).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the request succeeded.
operationNoThe operation performed (generate or presets).
resultNoFor generate, the policy artifacts; for presets, a presets array.
Behavior5/5

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

Describes determinism, pure compute, read-only, non-destructive, no external service contact, rate limit (30/min for anonymous), and output format, adding value beyond annotations.

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

Conciseness5/5

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

Information is front-loaded, each sentence serves a purpose, no redundancy, and well-structured despite length.

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

Completeness5/5

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

With an output schema and full parameter descriptions, the description covers purpose, usage, behavior, and output, leaving no gaps for an agent.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3. Description adds context for the operation parameter (generate vs presets) and clarifies usage, boosting it to 4.

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

Purpose5/5

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

Clearly states it generates a password policy document and validators, and distinguishes from sibling tools like crypto_password_generator and crypto_password_strength.

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

Usage Guidelines5/5

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

Explicitly states when to use this tool versus alternatives, and describes the two operations (generate and presets) with clear usage context.

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/Jambozx/onlinecybertools-mcp-server'

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