string_case
Convert text between camelCase, snake_case, kebab-case, PascalCase, and more.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/string-case.md
What string_case does on UnClick
AI agents call string_case to retrieve information from UnClick 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 |
|---|---|---|---|
text | string | Yes | Text to convert. |
Parameters from the server's own tool schema.
Why string_case is rated Low
This tool performs stateless string case conversion only. It takes text input and returns transformed text without querying databases, modifying external state, executing code, or triggering external operations. The operation is reversible and has no blast radius beyond potentially incorrect formatting if misused by an agent.
From the tool's definition Tool description states it 'Convert[s] text between camelCase, snake_case, kebab-case, PascalCase, and more' — a pure text transformation utility with no side effects, data retrieval, code execution, or state modification.
Attacks that exploit this kind of access
The rule that runs string_case 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 string_case, this is the rule to start with:
string_case 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 UnClick, apply this rule, and every string_case call is checked against it from then on.
Questions about string_case
Convert text between camelCase, snake_case, kebab-case, PascalCase, and more. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
string_case accepts 1 parameter: text. Required: text. 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 string_case: 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.
string_case 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 string_case 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 string_case. 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.
string_case 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