AI agents use generate_memorable 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 |
|---|---|---|---|
pattern | string | — | Pattern: c=consonant, v=vowel, d=digit, s=symbol |
Parameters from the server's own tool schema.
An AI agent can call generate_memorable faster than any human can review — one bad instruction and it creates or modifies resources in TinyFn by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Generate a memorable password based on a pattern. 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_memorable accepts 1 parameter: pattern. 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_memorable: 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_memorable 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_memorable 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_memorable. 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_memorable 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.
generate_memorable is one line of TinyFn's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →