text_transform
Transform text (uppercase, lowercase, title case, slug, etc.).
This record as markdown: /tools/creativelead-unclick/text-transform.md
What text_transform does on UnClick
AI agents invoke text_transform to trigger actions in UnClick. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | — | |
transform | string | — | uppercase, lowercase, titlecase, slug, reverse, etc. |
Parameters from the server's own tool schema.
Why text_transform is rated High
This tool executes a transformation operation on input text. It doesn't read external data, write/persist anything, or delete anything — it processes input and returns output. 'Execute' best fits since it performs a computational operation (text processing) whose output depends on the arguments. Severity is low as misuse has minimal blast radius — it only transforms text strings with no external side effects.
From the tool's definition Transform text (uppercase, lowercase, title case, slug, etc.)
Attacks that exploit this kind of access
The rule that runs text_transform 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 text_transform, this is the rule to start with:
text_transform stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 text_transform call is checked against it from then on.
Questions about text_transform
Transform text (uppercase, lowercase, title case, slug, etc.). It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
text_transform accepts 2 parameters: text, transform. 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 text_transform: 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.
text_transform is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the text_transform 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 text_transform. 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.
text_transform is provided by the UnClick MCP server (creativelead/unclick). 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.
Across the catalogue