password_strength
Offline password strength audit (POST only, so the password never appears in a URL or access log; never echoed or stored): zxcvbn-style score 0-4, estimated guesses and entropy, crack-time estimates, weak patterns (common/breached passwords incl. l33t and reversed, keyboard walks, sequences, repe...
This record as markdown: /tools/com-it-scorptech-x402/password-strength.md
What password_strength does on ScorpTech x402 API
AI agents call password_strength to retrieve information from ScorpTech x402 API 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, 1-256 chars (JSON body only; never returned) |
user_inputs | array | — | Optional personal context (username, email, name) that should not appear in the password |
Parameters from the server's own tool schema.
Why password_strength is rated Low
Even though password_strength only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHandles credentials or secrets (password)
Attacks that exploit this kind of access
The rule that runs password_strength safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For password_strength, this is the rule to start with:
password_strength 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 ScorpTech x402 API, apply this rule, and every password_strength call is checked against it from then on.
Questions about password_strength
Offline password strength audit (POST only, so the password never appears in a URL or access log; never echoed or stored): zxcvbn-style score 0-4, estimated guesses and entropy, crack-time estimates, weak patterns (common/breached passwords incl. l33t and reversed, keyboard walks, sequences, repeats, dates, personal info) and NIST SP 800-63B checks. Body: { "password": "...", "user_inputs"?: ["alice", "alice@example.com"] }. Price: $0.005 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/password-strength. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
password_strength accepts 2 parameters: password, user_inputs. Required: password. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for password_strength: 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 ScorpTech x402 API. Nothing to install.
password_strength 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_strength 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_strength. 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_strength is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue