manage_collection_products · AdminAgent MCP: Risk & Policy

WHAT IT DOES

What manage_collection_products does on AdminAgent

AI agents use manage_collection_products 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 manage_collection_products needs a policy

The tool name suggests modification of product-collection relationships (adding/removing products from collections). This is a reversible data modification operation (Write category). Severity is high because misuse could reorganize product catalog visibility, affecting sales and customer navigation.

From the tool's definition Tool name 'manage_collection_products' combined with server context 'full store management' and sibling tools like 'activate_discount' and 'adjust_inventory' that are Write/Execute operations. The description is empty, limiting certainty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_collection_products Rate-limited

manage_collection_products 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": {
    "manage_collection_products": {
      "limits": [
        {
          "counter": "manage_collection_products_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 manage_collection_products

What does the manage_collection_products tool do? +

manage_collection_products. 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 manage_collection_products? +

Register the AdminAgent MCP server in PolicyLayer and add a rule for manage_collection_products: 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 manage_collection_products? +

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

Can I rate-limit manage_collection_products? +

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

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

manage_collection_products 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.