set_current_profile · Amazon Ads MCP: Risk & Policy

WHAT IT DOES

What set_current_profile does on Amazon Ads MCP

AI agents use set_current_profile to create or update resources in Amazon Ads MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amazon Ads MCP environment.

WHY IT NEEDS A POLICY

Why set_current_profile needs a policy

This tool writes/modifies application state (the current profile context) in a reversible manner. While it does not directly modify Amazon Ads campaign data, it changes configuration that subsequent operations depend on. The severity is medium because incorrect profile selection could cause queries and operations to target the wrong advertiser account, but the change is reversible (can set a different profile).

From the tool's definition Tool description states 'Set the current working profile context' and 'will be used automatically for all subsequent' operations. This modifies the active profile state that affects downstream operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_current_profile Rate-limited

set_current_profile 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": {
    "set_current_profile": {
      "limits": [
        {
          "counter": "set_current_profile_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 Amazon Ads MCP, so you can run agents against it safely.

FAQ

Questions about set_current_profile

What does the set_current_profile tool do? +

Set the current working profile context. This profile will be used automatically for all subsequent campaign, keyword, and performance queries. It is categorised as a Write tool in the Amazon Ads MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_current_profile? +

Register the Amazon Ads MCP server in PolicyLayer and add a rule for set_current_profile: 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 Amazon Ads MCP. Nothing to install.

What risk level is set_current_profile? +

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

Can I rate-limit set_current_profile? +

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

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

set_current_profile is provided by the Amazon Ads MCP server (ppcprophet/amazon-ads-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.