publish_resource · AdminAgent MCP: Risk & Policy

WHAT IT DOES

What publish_resource does on AdminAgent

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

Publishing a product, collection, or page to a sales channel is a reversible write operation that modifies the visibility and accessibility of store resources. It creates or updates the published state of these resources but does not irreversibly delete data (Destructive), does not transfer money (Financial), does not execute arbitrary code (Execute), and is more than passive retrieval (Read).

From the tool's definition Tool description: 'Publish a resource (product, collection, page) to a sales channel.' The word 'Publish' indicates a state change that makes resources publicly visible and available for sale.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

publish_resource Rate-limited

publish_resource 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": {
    "publish_resource": {
      "limits": [
        {
          "counter": "publish_resource_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 publish_resource

What does the publish_resource tool do? +

Publish a resource (product, collection, page) to a sales channel. 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 publish_resource? +

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

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

Can I rate-limit publish_resource? +

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

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

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