Critical Risk →

json_clear

Clear container at path (array or object). Args: key: The name of the key path: The path in the JSON document Returns: Success message or error message

Accepts file system path (path)

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

AI agents may call json_clear to permanently remove or destroy resources in Awslabs Valkey. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call json_clear in a loop, permanently destroying resources in Awslabs Valkey. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

amazon-elasticache-memorydb-valkey-mcp-server.yaml
tools:
  json_clear:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Awslabs Valkey policy for all 105 tools.

Tool Name json_clear
Category Destructive
Risk Level Critical

View all 105 tools →

Agents calling destructive-class tools like json_clear 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 Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

json_clear is one of the critical-risk operations in Awslabs Valkey. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the json_clear tool do? +

Clear container at path (array or object). Args: key: The name of the key path: The path in the JSON document Returns: Success message or error message. It is categorised as a Destructive tool in the Awslabs Valkey MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on json_clear? +

Add a rule in your Intercept YAML policy under the tools section for json_clear. 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_clear? +

json_clear is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit json_clear? +

Yes. Add a rate_limit block to the json_clear 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_clear completely? +

Set action: deny in the Intercept policy for json_clear. 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_clear? +

json_clear 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.