AI agents call to_upper_case to retrieve information from TinyFn without modifying anything — 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.
This tool takes input text and returns it in uppercase. It is a stateless, deterministic transformation with no side effects, analogous to a read/query operation. Misuse potential is negligible.
From the tool's definition 'Convert text to UPPERCASE' — pure string transformation with no side effects, no data storage, no external operations.
Attacks that exploit this kind of access
Convert text to UPPERCASE. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
to_upper_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_upper_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_upper_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_upper_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_upper_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_upper_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.
to_upper_case is one line of TinyFn's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →