add_attachments_to_set
AI agents use add_attachments_to_set 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 name suggests creating or modifying a relationship between attachments and a set, which is a reversible Write operation. However, confidence is reduced to 0.6 because the description is empty and the tool's exact behavior is unclear. Without more context, it could potentially be a Read operation if it merely retrieves attachments, but the verb 'add' strongly implies modification.
From the tool's definition Tool name 'add_attachments_to_set' indicates a create/modify operation that appends or associates attachments with a dataset or collection.
Attacks that exploit this kind of access
add_attachments_to_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 add_attachments_to_set: 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.
add_attachments_to_set 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 add_attachments_to_set 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 add_attachments_to_set. 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.
add_attachments_to_set 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.