inverse_case
Inverse the case of each character (same as swap).
This record as markdown: /tools/io-tinyfn-tinyfn/inverse-case.md
What inverse_case does on TinyFn
AI agents call inverse_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 inverse_case is rated Low
This is a string transformation utility that reads input and returns output without modifying any data, executing code, or causing side effects. It belongs in the Read category as a data transformation/query tool. Severity is low because misuse cannot cause harm - worst case is incorrect output formatting. Confidence is high given the straightforward nature of case inversion as a deterministic utility function.
From the tool's definition Tool inverts character case - a pure transformation function with no side effects. Description indicates deterministic operation ('same as swap') on character data.
Attacks that exploit this kind of access
The rule that runs inverse_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 inverse_case, this is the rule to start with:
inverse_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 inverse_case call is checked against it from then on.
Questions about inverse_case
Inverse the case of each character (same as swap). It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
inverse_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 inverse_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.
inverse_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 inverse_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 inverse_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.
inverse_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