filename_safe

Convert a string to a safe filename.

SERVERTinyFn SOURCEhttps://api.tinyfn.io/mcp/all/

Low RISK CLASS

Category Read

Parameters 31 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-tinyfn-tinyfn/filename-safe.md

WHAT IT DOES

What filename_safe does on TinyFn

AI agents call filename_safe 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
`filename`	string	Yes	Filename to sanitize
`max_length`	integer	—	Maximum filename length
`replacement`	string	—	Character to replace invalid chars with

Parameters from the server's own tool schema.

RISK

Why filename_safe is rated Low

This tool performs a deterministic string transformation (sanitizing a string into a safe filename). It reads input and returns a transformed output with no side effects, no data written, no execution, and no financial implications.

From the tool's definition Convert a string to a safe filename

Risk signalsAccepts file system path (filename)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs filename_safe 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 filename_safe, this is the rule to start with:

filename_safe Allowed

filename_safe is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "filename_safe": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect TinyFn, apply this rule, and every filename_safe call is checked against it from then on.

FAQ

Questions about filename_safe

What does the filename_safe tool do? +

Convert a string to a safe filename. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.

What parameters does filename_safe accept? +

filename_safe accepts 3 parameters: filename, max_length, replacement. Required: filename. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on filename_safe? +

Register the TinyFn MCP server in PolicyLayer and add a rule for filename_safe: 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.

What risk level is filename_safe? +

filename_safe is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit filename_safe? +

Yes. Add a rate_limit block to the filename_safe 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.

How do I block filename_safe completely? +

Set action: deny in the PolicyLayer policy for filename_safe. 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.

What MCP server provides filename_safe? +

filename_safe 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.

KEEP EXPLORING

More on TinyFn, and thousands of servers like it.

This server

All 572 TinyFn tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →