This record as markdown: /tools/io-tinyfn-tinyfn/extract-urls.md
What extract_urls does on TinyFn
AI agents call extract_urls 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 | The text to extract from |
Parameters from the server's own tool schema.
Why extract_urls is rated Low
This is a text analysis tool that reads input and returns extracted data. It has no side effects, performs no external operations, and does not modify or delete data. It falls squarely into the Read category with low severity since misuse would only result in information disclosure of URLs already present in the input text.
From the tool's definition Tool name 'extract_urls' and description 'Extract all URLs from text' indicate a retrieval operation that parses and returns URLs from input text without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
The rule that runs extract_urls 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 extract_urls, this is the rule to start with:
extract_urls 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 extract_urls call is checked against it from then on.
Questions about extract_urls
Extract all URLs from text. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
extract_urls 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 extract_urls: 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.
extract_urls 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 extract_urls 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 extract_urls. 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.
extract_urls 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