Remove member from set.
AI agents use set_remove to create or update resources in Amazon MQ MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amazon MQ MCP Server environment.
The tool modifies data by removing a member from a set, which is a Write operation (reversible modification). It is not a Read (no retrieval only), not Execute (no arbitrary code/commands), not Destructive (the removed member can be re-added), and not Financial.
From the tool's definition Tool name 'set_remove' and description 'Remove member from set' indicate a modification operation that removes data from a collection. This is a reversible write operation.
Attacks that exploit this kind of access
Remove member from set. It is categorised as a Write tool in the Amazon MQ MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Amazon MQ MCP Server MCP server in PolicyLayer and add a rule for set_remove: 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 MQ MCP Server. Nothing to install.
set_remove 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 set_remove 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 set_remove. 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.
set_remove is provided by the Amazon MQ MCP Server MCP server (awslabs.amazon-mq-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.