Medium Risk

create_lead_gen_site

Create a third-party LEAD-GENERATION page about a business (NOT a site for that business itself). Use this when the goal is to drive qualified search traffic to someone else's business — affiliate pages, review/guide pages, niche directories. The page is branded as an outside guide (e.g. "Best Ro...

Risk signalsHigh parameter count (12 properties)

Part of the WebZum - The Hosting Layer for AI-Generated Web Content server.

create_lead_gen_site can modify WebZum - The Hosting Layer for AI-Generated Web Content data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE WEBZUM - THE HOSTING LAYER FOR AI-GENERATED WEB CONTENT →

Free to start. No card required.

AI agents use create_lead_gen_site to create or modify resources in WebZum - The Hosting Layer for AI-Generated Web Content. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call create_lead_gen_site repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach WebZum - The Hosting Layer for AI-Generated Web Content.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_lead_gen_site": {
      "limits": [
        {
          "counter": "create_lead_gen_site_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full WebZum - The Hosting Layer for AI-Generated Web Content policy for all 16 tools.

Get this rule live on your own WebZum - The Hosting Layer for AI-Generated Web Content server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY WEBZUM - THE HOSTING LAYER FOR AI-GENERATED WEB CONTENT →

View all 16 tools →

These attack patterns abuse exactly the kind of access create_lead_gen_site gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so create_lead_gen_site only ever does what you allow.

SECURE WEBZUM - THE HOSTING LAYER FOR AI-GENERATED WEB CONTENT →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the create_lead_gen_site tool do? +

Create a third-party LEAD-GENERATION page about a business (NOT a site for that business itself). Use this when the goal is to drive qualified search traffic to someone else's business — affiliate pages, review/guide pages, niche directories. The page is branded as an outside guide (e.g. "Best Roofers in San Diego"), refers to the business in the third person, and routes CTAs to the business's existing website. Differences from create_site: - Slug + page brand are SEO-vanity (e.g. "best-roofers-sandiego"), not the candidate's brand name. - Voice is third-party guide/reviewer — never first person. - Primary CTA is "visit their website"; phone/email demoted. - No specific pricing quoted; differentiators emphasized. - Locality is judged by category, not just address (IT/SaaS/agency stays category-wide even when a city is on file). Pass a business candidate object from search_businesses — that business is the one being PROMOTED. Requires authentication via API key (Bearer token). Generate an API key at webzum.com/dashboard/account-settings. The page generation happens in the background. Use get_site_status to check progress. Returns the businessId (a vanity slug) which can be used to access the page at /build/{businessId}.. It is categorised as a Write tool in the WebZum - The Hosting Layer for AI-Generated Web Content MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_lead_gen_site? +

Register the WebZum - The Hosting Layer for AI-Generated Web Content MCP server in PolicyLayer and add a rule for create_lead_gen_site: 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 WebZum - The Hosting Layer for AI-Generated Web Content. Nothing to install.

What risk level is create_lead_gen_site? +

create_lead_gen_site is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_lead_gen_site? +

Yes. Add a rate_limit block to the create_lead_gen_site 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 create_lead_gen_site completely? +

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

create_lead_gen_site is provided by the WebZum - The Hosting Layer for AI-Generated Web Content MCP server (https://webzum.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every WebZum - The Hosting Layer for AI-Generated Web Content tool call.

Deterministic rules across all 16 WebZum - The Hosting Layer for AI-Generated Web Content tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.