create_collection · AdminAgent MCP: Risk & Policy

WHAT IT DOES

What create_collection does on AdminAgent

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

WHY IT NEEDS A POLICY

Why create_collection needs a policy

This tool creates a new collection, which is a reversible write operation in Shopify—collections can be edited or deleted. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or move money (would be Financial). The blast radius is medium: miscreated collections clutter the store and could affect customer navigation, but can be undone without data loss or financial impact.

From the tool's definition Tool name 'create_collection' indicates creation of a new collection in a Shopify store. Given the server context (Shopify Admin via Claude + MCP), this creates a data record within the store's product organization system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_collection Rate-limited

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

FAQ

Questions about create_collection

What does the create_collection tool do? +

create_collection. It is categorised as a Write tool in the AdminAgent 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_collection? +

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

What risk level is create_collection? +

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

Can I rate-limit create_collection? +

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

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

create_collection is provided by the AdminAgent MCP server (rushikeshmore/admin-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.