Add attachments to a new or existing attachment set. ## Usage - Use before create_support_case or add_communication_to_case - Pass the returned attachmentSetId to those tools - Attachment sets expire after 1 hour; each file must be < 5MB - The `data` field must be the file contents as a base64-e...
Part of the AWS Support MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use add_attachments_to_set to create or modify resources in AWS Support MCP Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call add_attachments_to_set repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach AWS Support MCP Server.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
add_attachments_to_set:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full AWS Support MCP Server policy for all 11 tools.
Agents calling write-class tools like add_attachments_to_set have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Add attachments to a new or existing attachment set. ## Usage - Use before create_support_case or add_communication_to_case - Pass the returned attachmentSetId to those tools - Attachment sets expire after 1 hour; each file must be < 5MB - The `data` field must be the file contents as a base64-encoded string - The server decodes it to raw bytes before sending to AWS (the SDK handles wire encoding) - Do NOT double-encode: encode the raw file bytes to base64 exactly once ## Example ``` add_attachments_to_set( attachments=[{'fileName': 'error.log', 'data': '<base64-encoded-file-contents>'}] ) ```. It is categorised as a Write tool in the AWS Support MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for add_attachments_to_set. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS Support MCP Server MCP server.
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 Intercept 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 Intercept 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 AWS Support MCP Server MCP server (awslabs.aws-support-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.