Medium Risk

json_set

Set the JSON value at path. Args: key: The name of the key path: The path in the JSON document (e.g., "$.name" or "." for root) value: The value to set nx: Only set if path doesn't exist xx: Only set if path exists Returns: Success message or error message

Accepts file system path (path); Admin/system-level operation

Part of the Awslabs Valkey MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use json_set to create or modify resources in Awslabs Valkey. 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 json_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 Awslabs Valkey.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

amazon-elasticache-memorydb-valkey-mcp-server.yaml
tools:
  json_set:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Awslabs Valkey policy for all 105 tools.

Tool Name json_set
Category Write
Risk Level Medium

View all 105 tools →

Agents calling write-class tools like json_set have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the json_set tool do? +

Set the JSON value at path. Args: key: The name of the key path: The path in the JSON document (e.g., "$.name" or "." for root) value: The value to set nx: Only set if path doesn't exist xx: Only set if path exists Returns: Success message or error message. 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 json_set? +

Add a rule in your Intercept YAML policy under the tools section for json_set. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Awslabs Valkey MCP server.

What risk level is json_set? +

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

Can I rate-limit json_set? +

Yes. Add a rate_limit block to the json_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.

How do I block json_set completely? +

Set action: deny in the Intercept policy for json_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.

What MCP server provides json_set? +

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

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.