Update the status of a keyword (pause, enable, or archive)
AI agents use update_keyword_status 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.
This tool creates or modifies data reversibly—pausing, enabling, or archiving keywords can be undone by changing status back. It does not irreversibly delete (Destructive) nor move money (Financial). While it affects ad campaign performance, the action is reversible, making it a Write operation.
From the tool's definition Tool name 'update_keyword_status' with description 'Update the status of a keyword (pause, enable, or archive)' directly modifies keyword state in Amazon Sponsored Ads campaigns.
Attacks that exploit this kind of access
Update the status of a keyword (pause, enable, or archive). 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.
Register the Amazon Ads MCP server in PolicyLayer and add a rule for update_keyword_status: 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.
update_keyword_status is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_keyword_status 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.
Set action: deny in the PolicyLayer policy for update_keyword_status. 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.
update_keyword_status 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →