text_case
Text Case Converter — Convert any identifier or sentence to snake_case, kebab-case, camelCase, PascalCase, CONSTANT_CASE, or Title Case.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/text-case.md
What text_case does on Gateway
AI agents call text_case to retrieve information from Gateway 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 |
target | string | Yes | Target case |
Parameters from the server's own tool schema.
Why text_case is rated Low
This is a pure transformation function that accepts text and returns reformatted text. It performs no data mutation, deletion, execution, financial operations, or external side effects. It is strictly a Read operation — a deterministic computation that retrieves/transforms data without modifying any state or system.
From the tool's definition Tool name 'text_case' and description 'Convert any identifier or sentence to snake_case, kebab-case, camelCase, PascalCase, CONSTANT_CASE, or Title Case' indicates a text transformation utility that reads input and returns formatted output with no side…
Attacks that exploit this kind of access
The rule that runs text_case safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For text_case, this is the rule to start with:
text_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 Gateway, apply this rule, and every text_case call is checked against it from then on.
Questions about text_case
Text Case Converter — Convert any identifier or sentence to snake_case, kebab-case, camelCase, PascalCase, CONSTANT_CASE, or Title Case. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
text_case accepts 2 parameters: text, target. Required: text, target. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for text_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 Gateway. Nothing to install.
text_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 text_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 text_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.
text_case is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue