AI agents use string_mset to create or update resources in Redis MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Redis MCP environment.
This tool creates or modifies multiple string key-value pairs in Redis. While reversible (data can be overwritten or deleted later), it alters stored state and could corrupt application data if invoked with incorrect arguments.
From the tool's definition Tool name 'string_mset' and description '批量设置键值' (batch set key-value pairs) indicate bulk modification of string data in Redis.
Attacks that exploit this kind of access
批量设置键值. It is categorised as a Write tool in the Redis MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Redis MCP server in PolicyLayer and add a rule for string_mset: 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. Nothing to install.
string_mset 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 string_mset 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 string_mset. 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.
string_mset is provided by the Redis MCP server (pickstar-2002/redis-mcp). 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 →