resolve_support_case
AI agents use resolve_support_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.
The tool appears to update a support case record, which is a reversible data modification (cases can typically be reopened). This falls under Write rather than Execute or Destructive. Severity is medium because resolving support cases could impact customer communication workflows, but the action is reversible. Confidence is lowered due to the absent description.
From the tool's definition Tool name 'resolve_support_case' suggests modifying support case state from unresolved to resolved. The empty description prevents definitive assessment, but the verb 'resolve' indicates a state change operation.
Attacks that exploit this kind of access
resolve_support_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.
Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for resolve_support_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.
resolve_support_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 resolve_support_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 resolve_support_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.
resolve_support_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.