list_locales
List available locales for Faker-powered endpoints.
This record as markdown: /tools/io-tinyfn-tinyfn/list-locales.md
What list_locales does on TinyFn
AI agents call list_locales 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.
Why list_locales is rated Low
This tool retrieves or queries a static list of available locales without side effects, mutations, or external operations. It is a pure read operation typical of informational endpoints. The severity is low because listing locales poses minimal risk even if accessed by an AI agent; the information is non-sensitive and non-destructive.
From the tool's definition Tool name is 'list_locales' and description states 'List available locales' - uses list/query semantics with no modification or execution implied.
Attacks that exploit this kind of access
The rule that runs list_locales 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 list_locales, this is the rule to start with:
list_locales 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 list_locales call is checked against it from then on.
Questions about list_locales
List available locales for Faker-powered endpoints. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
Register the TinyFn MCP server in PolicyLayer and add a rule for list_locales: 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.
list_locales 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 list_locales 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 list_locales. 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.
list_locales 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