This record as markdown: /tools/io-tinyfn-tinyfn/detect-case.md
What detect_case does on TinyFn
AI agents call detect_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 analyze |
Parameters from the server's own tool schema.
Why detect_case is rated Low
This tool retrieves information about the formatting style of supplied text without altering data, executing code, or triggering side effects. It is analogous to other deterministic utility tools on the server (validation, analysis) that read and return results. The low severity reflects minimal blast radius—misuse would only return incorrect classification data.
From the tool's definition Tool performs text analysis ('detect the case style of text') with no modification, deletion, or execution of external operations. It is a pure query operation that examines input and returns case classification results.
Attacks that exploit this kind of access
The rule that runs detect_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 detect_case, this is the rule to start with:
detect_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 detect_case call is checked against it from then on.
Questions about detect_case
Detect the case style of text. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
detect_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 detect_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.
detect_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 detect_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 detect_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.
detect_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