This record as markdown: /tools/io-tinyfn-tinyfn/random-url.md
What random_url does on TinyFn
AI agents call random_url 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 |
|---|---|---|---|
count | integer | — | Number of URLs to generate |
Parameters from the server's own tool schema.
Why random_url is rated Low
This tool generates synthetic data (random URLs) deterministically using Faker library. It is a data generation utility with no destructive, financial, or execution capabilities. While 'generate' could suggest Write, this is fake data generation with no persistent storage implied—analogous to other deterministic utility functions on this server (math, conversion, hashing).
From the tool's definition Tool name is 'random_url' and description states 'Generate random URL(s) using Faker.' The tool generates/produces fake data with no side effects, does not modify system state, retrieve sensitive data, or trigger external operations.
Attacks that exploit this kind of access
The rule that runs random_url 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 random_url, this is the rule to start with:
random_url 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 random_url call is checked against it from then on.
Questions about random_url
Generate random URL(s) using Faker. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
random_url accepts 1 parameter: count. 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 random_url: 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.
random_url 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 random_url 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 random_url. 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.
random_url 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