This record as markdown: /tools/io-tinyfn-tinyfn/extract-domain.md
What extract_domain does on TinyFn
AI agents call extract_domain 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 extract domain from |
include_subdomain | boolean | — | Include subdomain in result |
Parameters from the server's own tool schema.
Why extract_domain is rated Low
This is a straightforward data extraction utility that reads and parses a URL to return its domain component. It performs no mutations, executions, or destructive operations. The blast radius of misuse is minimal—an agent could extract domain information from arbitrary URLs, but this poses no security, financial, or operational risk.
From the tool's definition Tool name 'extract_domain' and description 'Extract domain from a URL' indicate a retrieval/parsing operation with no side effects. The tool parses and returns information from a provided URL string without modifying, creating, or deleting any data.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs extract_domain 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_domain, this is the rule to start with:
extract_domain 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_domain call is checked against it from then on.
Questions about extract_domain
Extract domain from a URL. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
extract_domain accepts 2 parameters: url, include_subdomain. 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 extract_domain: 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_domain 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_domain 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_domain. 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_domain 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