password_policy_check
Password Policy Checker — Evaluate a password against configurable composition and blocklist rules (length, upper/lower/digit/symbol, common-password list) and list any violations.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/password-policy-check.md
What password_policy_check does on Gateway
AI agents call password_policy_check to retrieve information from Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
password | string | Yes | Password to evaluate |
max_length | integer | — | Maximum allowed length (default: no cap) |
min_length | integer | — | Minimum required length (default 8) |
require_digit | boolean | — | Require at least one digit (default true) |
require_lower | boolean | — | Require at least one lowercase letter (default true) |
require_upper | boolean | — | Require at least one uppercase letter (default true) |
require_symbol | boolean | — | Require at least one non-alphanumeric symbol (default false) |
disallow_common | boolean | — | Reject passwords on a common-password blocklist (default true) |
Parameters from the server's own tool schema.
Why password_policy_check is rated Low
This is a pure validation/query tool. It takes a password as input and returns compliance information (violations list). It has no side effects on systems, data persistence, or external state. The only risk is information disclosure if the tool leaks the checked password in logs, but that is a deployment concern, not an inherent capability risk.
From the tool's definition The tool 'Evaluate a password against configurable composition and blocklist rules' and 'list any violations' — it performs validation checks and returns results. No modifications, deletions, or external operations are triggered.
Risk signalsHandles credentials or secrets (password)
Attacks that exploit this kind of access
The rule that runs password_policy_check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For password_policy_check, this is the rule to start with:
password_policy_check is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every password_policy_check call is checked against it from then on.
Questions about password_policy_check
Password Policy Checker — Evaluate a password against configurable composition and blocklist rules (length, upper/lower/digit/symbol, common-password list) and list any violations. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
password_policy_check accepts 8 parameters: password, max_length, min_length, require_digit, require_lower, require_upper, require_symbol, disallow_common. Required: password. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for password_policy_check: 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 Gateway. Nothing to install.
password_policy_check is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the password_policy_check 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 password_policy_check. 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.
password_policy_check is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue