generate_webcomponent · Mozaic MCP Server MCP: Risk & Policy

WHAT IT DOES

What generate_webcomponent does on Mozaic MCP Server

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

WHY IT NEEDS A POLICY

Why generate_webcomponent needs a policy

This tool generates Web Component code snippets as output text/code, which qualifies as content creation (Write category). The generated code is inert HTML/JavaScript that must be separately integrated or executed by a user; the tool itself does not execute the generated code, delete data, modify persistent systems, or move money.

From the tool's definition Tool performs code generation ('Generate ready-to-use Web Component code', 'Returns HTML with custom elements and import statement'), creating artifacts that are written but not automatically executed or persisted.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_webcomponent Rate-limited

generate_webcomponent 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_webcomponent": {
      "limits": [
        {
          "counter": "generate_webcomponent_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 Mozaic MCP Server, so you can run agents against it safely.

FAQ

Questions about generate_webcomponent

What does the generate_webcomponent tool do? +

Generate ready-to-use Web Component code using Mozaic Design System (@adeo/mozaic-web-components). Returns HTML with custom elements and import statement. It is categorised as a Write tool in the Mozaic 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_webcomponent? +

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

What risk level is generate_webcomponent? +

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

Can I rate-limit generate_webcomponent? +

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

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

generate_webcomponent is provided by the Mozaic MCP Server MCP server (merzoukemansouri/adeo-mozaic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.