generate_password_2
Generate a secure random password.
This record as markdown: /tools/io-tinyfn-tinyfn/generate-password-2.md
What generate_password_2 does on TinyFn
AI agents use generate_password_2 to create or update resources in TinyFn, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TinyFn environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
digits | boolean | — | Include digits |
length | integer | — | Password length |
special | boolean | — | Include special characters |
lowercase | boolean | — | Include lowercase letters |
uppercase | boolean | — | Include uppercase letters |
exclude_chars | string | — | Additional characters to exclude |
exclude_ambiguous | boolean | — | Exclude ambiguous chars (0O1lI) |
Parameters from the server's own tool schema.
Why generate_password_2 is rated Medium
This tool generates data rather than retrieving or querying existing information. However, the generated password is informational output with no persistent side effects on external systems—it does not modify application state, create accounts, or trigger authentication changes. Therefore it is Write (data creation) rather than Execute or higher.
From the tool's definition Tool name 'generate_password_2' and description 'Generate a secure random password' indicate it creates new data (a password string) that would typically be stored or used by an application.
Attacks that exploit this kind of access
The rule that runs generate_password_2 safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TinyFn, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For generate_password_2, this is the rule to start with:
generate_password_2 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 TinyFn, apply this rule, and every generate_password_2 call is checked against it from then on.
Questions about generate_password_2
Generate a secure random password. It is categorised as a Write tool in the TinyFn MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
generate_password_2 accepts 7 parameters: digits, length, special, lowercase, uppercase, exclude_chars, exclude_ambiguous. The full parameter table on this page comes from the server's own tool schema.
Register the TinyFn MCP server in PolicyLayer and add a rule for generate_password_2: 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 TinyFn. Nothing to install.
generate_password_2 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 generate_password_2 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 generate_password_2. 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.
generate_password_2 is provided by the TinyFn MCP server (https://api.tinyfn.io/mcp/all/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TinyFn, and thousands of servers like it.
This server
Across the catalogue