add_communication_to_case
AI agents use add_communication_to_case 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 'add_' prefix and context of 'communication' and 'case' suggest this tool creates or appends a new communication record to an existing case, which is a reversible modification of data. This is a Write operation rather than Read (no retrieval implied), Execute (no code/command execution), Destructive (reversible), or Financial.
From the tool's definition Tool name 'add_communication_to_case' indicates adding/appending communication content to a support case; 'add_' prefix suggests a Write operation that creates or modifies data.
Attacks that exploit this kind of access
add_communication_to_case. 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_communication_to_case: 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_communication_to_case 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_communication_to_case 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_communication_to_case. 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_communication_to_case 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.