create_return · AdminAgent MCP: Risk & Policy

WHAT IT DOES

What create_return does on AdminAgent

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

Creating a return in Shopify modifies order/inventory state and customer records—a reversible write operation. It does not delete data (would be Destructive), execute arbitrary code (Execute), or move funds (Financial). The medium severity reflects potential for customer-facing disruption or incorrect refund liability if misused, but returns are typically reversible through system corrections or reversal actions.

From the tool's definition Tool name 'create_return' on a Shopify Admin MCP server; sibling tools include 'cancel_order', 'capture_payment', and 'adjust_inventory', indicating write/modify operations on e-commerce data. Empty description lowers specificity.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_return Rate-limited

create_return 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_return": {
      "limits": [
        {
          "counter": "create_return_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_return

What does the create_return tool do? +

create_return. 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_return? +

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

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

Can I rate-limit create_return? +

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

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

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