generate_component · Website Builder MCP Server MCP

WHAT IT DOES

What generate_component does on Website Builder MCP Server

AI agents use generate_component to create or update resources in Website Builder MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Website Builder MCP Server environment.

WHY IT NEEDS A POLICY

Why generate_component needs a policy

This tool creates or modifies website components by generating HTML—a reversible action typical of Write category tools. While it produces output, it does not execute arbitrary code, delete data irreversibly, or move financial resources. The severity is low because generated HTML components are easily modified or removed without cascading damage to the system.

From the tool's definition Tool description states 'Generate HTML component' which creates new content (navbar, footer, etc.) without permanent data destruction. The verb 'generate' and the context of website building indicate content creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_component Rate-limited

generate_component stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_component": {
      "limits": [
        {
          "counter": "generate_component_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about generate_component

What does the generate_component tool do? +

Generate HTML component (navbar, footer, etc.). It is categorised as a Write tool in the Website Builder MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on generate_component? +

Register the Website Builder MCP Server MCP server in PolicyLayer and add a rule for generate_component: 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 Website Builder MCP Server. Nothing to install.

What risk level is generate_component? +

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

Can I rate-limit generate_component? +

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

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

generate_component is provided by the Website Builder MCP Server MCP server (pmkhairnarr/website-builder-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.