add_registry_item · Zola MCP: Risk & Policy

WHAT IT DOES

What add_registry_item does on Zola

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

WHY IT NEEDS A POLICY

Why add_registry_item needs a policy

An AI agent can call add_registry_item faster than any human can review — one bad instruction and it creates or modifies resources in Zola by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_registry_item Rate-limited

add_registry_item 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": {
    "add_registry_item": {
      "limits": [
        {
          "counter": "add_registry_item_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 Zola, so you can run agents against it safely.

FAQ

Questions about add_registry_item

What does the add_registry_item tool do? +

Add a product (by SKU) to the registry. If collection_id is omitted, the default collection is looked up automatically. It is categorised as a Write tool in the Zola MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_registry_item? +

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

What risk level is add_registry_item? +

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

Can I rate-limit add_registry_item? +

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

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

add_registry_item is provided by the Zola MCP server (zola-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.