password_generate
Generate a cryptographically secure random password.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/password-generate.md
What password_generate does on UnClick
AI agents use password_generate to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
digits | boolean | — | Include digits (default true). |
length | number | — | Password length (4-128, default 16). |
symbols | boolean | — | Include symbols (default true). |
lowercase | boolean | — | Include lowercase letters (default true). |
uppercase | boolean | — | Include uppercase letters (default true). |
Parameters from the server's own tool schema.
Why password_generate is rated Medium
This tool creates a new password, which is a Write operation. It has no destructive effects (passwords are easily discarded or regenerated), does not execute arbitrary code or external operations, does not move money, and does not retrieve sensitive data. The blast radius is minimal—a generated password is just output data that the user controls whether to adopt.
From the tool's definition Tool is named 'password_generate' and described as 'Generate a cryptographically secure random password.' The action is to generate/create a new password artifact.
Attacks that exploit this kind of access
The rule that runs password_generate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For password_generate, this is the rule to start with:
password_generate stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every password_generate call is checked against it from then on.
Questions about password_generate
Generate a cryptographically secure random password. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
password_generate accepts 5 parameters: digits, length, symbols, lowercase, uppercase. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for password_generate: 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 UnClick. Nothing to install.
password_generate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the password_generate 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_generate. 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_generate is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue