build_url_2 · TinyFn MCP: Risk & Policy

WHAT IT DOES

What build_url_2 does on TinyFn

AI agents invoke build_url_2 to trigger actions in TinyFn. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

PARAMETERS

Parameter	Type	Required	Description
`host`	string	Yes	Hostname
`path`	string	—	URL path
`port`	integer	—	Port number
`query`	string	—	Query string (without ?)
`scheme`	string	—	URL scheme

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why build_url_2 needs a policy

build_url_2 triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Risk signalsAccepts file system path (path) · Accepts URL/endpoint input (host)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

build_url_2 Rate-limited

build_url_2 stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "build_url_2": {
      "limits": [
        {
          "counter": "build_url_2_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches TinyFn, so you can run agents against it safely.

FAQ

Questions about build_url_2

What does the build_url_2 tool do? +

Build a URL from components. It is categorised as a Execute tool in the TinyFn MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does build_url_2 accept? +

build_url_2 accepts 5 parameters: host, path, port, query, scheme. Required: host. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on build_url_2? +

Register the TinyFn MCP server in PolicyLayer and add a rule for build_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.

What risk level is build_url_2? +

build_url_2 is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit build_url_2? +

Yes. Add a rate_limit block to the build_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.

How do I block build_url_2 completely? +

Set action: deny in the PolicyLayer policy for build_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.

What MCP server provides build_url_2? +

build_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.