manage_redirects · AdminAgent MCP: Risk & Policy

WHAT IT DOES

What manage_redirects does on AdminAgent

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

URL redirect management typically involves creating or modifying redirect rules, which are reversible data changes. This is a Write operation rather than Read (it's not merely querying redirects) or Execute (it's not arbitrary code execution, though bulk operations are mentioned on the server). High severity because misconfigured redirects can disrupt customer traffic and SEO, affecting store operations and revenue.

From the tool's definition Tool name 'manage_redirects' on a Shopify Admin server; context of 'full store management' including 'bulk operations' suggests capability to create, modify, or delete URL redirects. Description is empty, lowering confidence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_redirects Rate-limited

manage_redirects 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_redirects": {
      "limits": [
        {
          "counter": "manage_redirects_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_redirects

What does the manage_redirects tool do? +

manage_redirects. 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_redirects? +

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

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

Can I rate-limit manage_redirects? +

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

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

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