to_constant_case
Convert text to CONSTANT_CASE (alias for screaming snake).
This record as markdown: /tools/io-tinyfn-tinyfn/to-constant-case.md
What to_constant_case does on TinyFn
AI agents call to_constant_case to retrieve information from TinyFn 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 to_constant_case is rated Low
This tool performs a deterministic string formatting operation. It takes input text and returns a transformed version in CONSTANT_CASE format. There is no data persistence, no external calls, no reversible or irreversible modifications to any data store, and no code execution. This is a pure computational utility that retrieves (generates) formatted output without side effects, fitting the Read category definition.
From the tool's definition Tool description states 'Convert text to CONSTANT_CASE' - a text transformation/formatting function with no side effects, no data modification, no external operations.
Attacks that exploit this kind of access
The rule that runs to_constant_case 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 to_constant_case, this is the rule to start with:
to_constant_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 TinyFn, apply this rule, and every to_constant_case call is checked against it from then on.
Questions about to_constant_case
Convert text to CONSTANT_CASE (alias for screaming snake). It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
to_constant_case accepts 1 parameter: text. Required: text. 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 to_constant_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 TinyFn. Nothing to install.
to_constant_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 to_constant_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 to_constant_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.
to_constant_case 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