utm_builder
Append encoded UTM campaign parameters to a URL, preserving any existing query and fragment. Runs on smart-tools.xyz.
This record as markdown: /tools/io-github-9thshini-smart-tools/utm-builder.md
What utm_builder does on SmartTools
AI agents call utm_builder to retrieve information from SmartTools 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 | Base URL, e.g. https://example.com/landing |
term | string | — | utm_term (optional) |
locale | string | — | Language for the source_url link (default en) |
medium | string | Yes | utm_medium, e.g. cpc |
source | string | Yes | utm_source, e.g. google |
content | string | — | utm_content (optional) |
campaign | string | Yes | utm_campaign, e.g. spring_sale |
Parameters from the server's own tool schema.
Why utm_builder is rated Low
Even though utm_builder only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts URL/endpoint input (url) · Accepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs utm_builder safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SmartTools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For utm_builder, this is the rule to start with:
utm_builder 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 SmartTools, apply this rule, and every utm_builder call is checked against it from then on.
Questions about utm_builder
Append encoded UTM campaign parameters to a URL, preserving any existing query and fragment. Runs on smart-tools.xyz. It is categorised as a Read tool in the SmartTools MCP Server, which means it retrieves data without modifying state.
utm_builder accepts 7 parameters: url, term, locale, medium, source, content, campaign. Required: url, medium, source, campaign. The full parameter table on this page comes from the server's own tool schema.
Register the SmartTools MCP server in PolicyLayer and add a rule for utm_builder: 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 SmartTools. Nothing to install.
utm_builder 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 utm_builder 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 utm_builder. 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.
utm_builder is provided by the SmartTools MCP server (https://smart-tools.xyz/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SmartTools, and thousands of servers like it.
This server
Across the catalogue