password_hash
Hash, verify and identify password hashes — for seeding users, migrating auth systems, writing htpasswd files and auditing leaked hash formats. hash: bcrypt, Argon2id / Argon2i (where the server has libargon2), PBKDF2-SHA256 / SHA512 (Django format), SHA-512 / SHA-256 crypt (Linux shadow) and Apa...
This record as markdown: /tools/com-it-scorptech-x402/password-hash.md
What password_hash does on ScorpTech x402 API
AI agents call password_hash 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 |
|---|---|---|---|
cost | integer | — | bcrypt cost (default 12) |
hash | string | — | verify / identify: the stored hash |
mode | string | — | |
password | string | — | |
timeCost | integer | — | Argon2 iterations |
username | string | — | apr1: also return an htpasswd line |
algorithm | string | — | |
memoryKiB | integer | — | Argon2 memory (KiB) |
iterations | integer | — | PBKDF2 iterations (default OWASP: 600,000 SHA256 / 210,000 SHA512) or crypt rounds (default 656,000) |
Parameters from the server's own tool schema.
Why password_hash is rated Low
Even though password_hash 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_hash 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_hash, this is the rule to start with:
password_hash 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_hash call is checked against it from then on.
Questions about password_hash
Hash, verify and identify password hashes — for seeding users, migrating auth systems, writing htpasswd files and auditing leaked hash formats. hash: bcrypt, Argon2id / Argon2i (where the server has libargon2), PBKDF2-SHA256 / SHA512 (Django format), SHA-512 / SHA-256 crypt (Linux shadow) and Apache APR1 (htpasswd). verify: checks a password against bcrypt, Argon2, crypt ($1$ $5$ $6$, DES), APR1, Django / Werkzeug / passlib PBKDF2, phpass ($P$ $H$, WordPress), Drupal 7 ($S$), LDAP {SSHA} / {SHA} / {SSHA256} / {SSHA512} / {SMD5}, MySQL 4.1+ and unsalted MD5 / SHA / NTLM hex. identify: algorithm, parameters and a verdict against the OWASP Password Storage Cheat Sheet, with needsRehash. Passwords are never echoed or stored. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/password-hash. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
password_hash accepts 9 parameters: cost, hash, mode, password, timeCost, username, algorithm, memoryKiB, iterations. 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_hash: 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_hash 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_hash 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_hash. 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_hash 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