add_communication_to_case · Awslabs Valkey MCP

WHAT IT DOES

What add_communication_to_case does on Awslabs Valkey

AI agents use add_communication_to_case to create or update resources in Awslabs Valkey — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Awslabs Valkey environment.

WHY IT NEEDS A POLICY

Why add_communication_to_case needs a policy

The tool appears to add (create/append) communications to a case, which is a reversible modification of data. Without a description, confidence is reduced, but the naming convention clearly indicates a Write action rather than Read, Execute, or Destructive. Severity is medium because while communications can be added unintentionally, they are typically recoverable and do not result in data loss or financial impact.

From the tool's definition Tool name 'add_communication_to_case' indicates creating or appending a communication record to a support case. The 'add_' prefix suggests a Write operation that modifies case data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_communication_to_case Rate-limited

add_communication_to_case stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_communication_to_case": {
      "limits": [
        {
          "counter": "add_communication_to_case_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Awslabs Valkey, so you can run agents against it safely.

FAQ

Questions about add_communication_to_case

What does the add_communication_to_case tool do? +

add_communication_to_case. It is categorised as a Write tool in the Awslabs Valkey MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_communication_to_case? +

Register the Awslabs Valkey 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 Awslabs Valkey. Nothing to install.

What risk level is add_communication_to_case? +

add_communication_to_case is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_communication_to_case? +

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.

How do I block add_communication_to_case completely? +

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.

What MCP server provides add_communication_to_case? +

add_communication_to_case is provided by the Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.