update_marketing_consent · AdminAgent MCP: Risk & Policy

WHAT IT DOES

What update_marketing_consent does on AdminAgent

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

The 'update' prefix and focus on consent settings indicate this creates or modifies data reversibly (customer marketing preferences). This does not irreversibly delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read).

From the tool's definition Tool name 'update_marketing_consent' indicates modification of customer consent settings. The context of a Shopify Admin MCP server with bulk operations capabilities suggests this tool modifies customer data fields related to marketing preferences.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_marketing_consent Rate-limited

update_marketing_consent 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": {
    "update_marketing_consent": {
      "limits": [
        {
          "counter": "update_marketing_consent_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 update_marketing_consent

What does the update_marketing_consent tool do? +

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

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

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

Can I rate-limit update_marketing_consent? +

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

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

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