This record as markdown: /tools/io-tinyfn-tinyfn/camel-case.md
What camel_case does on TinyFn
AI agents call camel_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 | The text to convert |
Parameters from the server's own tool schema.
Why camel_case is rated Low
This is a simple, deterministic text conversion function. It retrieves/transforms data without modifying any state, creating irreversible changes, executing external code, or moving funds. It belongs in the Read category as a data retrieval/transformation tool with minimal security risk.
From the tool's definition Tool name 'camel_case' and description 'Convert text to camelCase' indicate a text transformation utility that reads input and returns formatted output with no side effects, no data persistence, and no external operations.
Attacks that exploit this kind of access
The rule that runs camel_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 camel_case, this is the rule to start with:
camel_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 camel_case call is checked against it from then on.
Questions about camel_case
Convert text to camelCase. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
camel_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 camel_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.
camel_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 camel_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 camel_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.
camel_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