This record as markdown: /tools/io-tinyfn-tinyfn/parse-url-2.md
What parse_url_2 does on TinyFn
AI agents call parse_url_2 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 |
|---|---|---|---|
url | string | Yes | URL to parse |
Parameters from the server's own tool schema.
Why parse_url_2 is rated Low
This tool only parses/decomposes a URL string into its constituent parts (scheme, host, path, query, etc.). It is a pure read/analysis operation with no side effects, no data modification, and no external calls. Misuse potential is minimal.
From the tool's definition Parse a URL into its components
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs parse_url_2 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 parse_url_2, this is the rule to start with:
parse_url_2 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 parse_url_2 call is checked against it from then on.
Questions about parse_url_2
Parse a URL into its components. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
parse_url_2 accepts 1 parameter: url. Required: url. 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 parse_url_2: 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.
parse_url_2 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 parse_url_2 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 parse_url_2. 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.
parse_url_2 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