json_set
AI agents use json_set to create or update resources in Redis MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Redis MCP Server environment.
This tool creates or modifies JSON data structures in Redis reversibly. While it changes state, it is not destructive (data can be updated or deleted afterward) and does not execute arbitrary code or move financial assets. The empty description lowers confidence slightly, but the name and server context clearly indicate a write operation with medium severity blast radius if misused to corrupt application data.
From the tool's definition Tool name 'json_set' indicates setting/modifying JSON data in Redis. Server description confirms 'manage and search data in Redis' including JSON support. Sibling tool 'delete' and operation context show write capabilities.
Attacks that exploit this kind of access
json_set. It is categorised as a Write tool in the Redis MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Redis MCP Server MCP server in PolicyLayer and add a rule for json_set: 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 Redis MCP Server. Nothing to install.
json_set 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 json_set 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 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.
json_set is provided by the Redis MCP Server MCP server (yuchenhui/mcp-redis). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →