Store a vector as a field in a Redis hash. Args: name: The Redis hash key. vector_field: The field name inside the hash. Unless specifically required, use the default field name vector: The vector (list of numbers) to store in the hash. Returns: True if the vector was successfully stored, False o...
AI agents use set_vector_in_hash 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 data in Redis by storing vector data in hash fields. It is reversible (the data can be updated or deleted later), making it a Write operation rather than Destructive. The severity is medium because an AI agent could maliciously overwrite legitimate vector data or fill storage with junk vectors, but the impact is limited to the hash fields being written and can be undone.
From the tool's definition Tool description states it 'Store[s] a vector as a field in a Redis hash', which is a data modification operation. The return value indicates success/failure of the storage operation.
Documented attack patterns abuse exactly the kind of access set_vector_in_hash gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Redis MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for set_vector_in_hash:
{
"version": "1",
"default": "deny",
"tools": {
"set_vector_in_hash": {
"limits": [
{
"counter": "set_vector_in_hash_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_vector_in_hash stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Store a vector as a field in a Redis hash. Args: name: The Redis hash key. vector_field: The field name inside the hash. Unless specifically required, use the default field name vector: The vector (list of numbers) to store in the hash. Returns: True if the vector was successfully stored, False otherwise. 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 set_vector_in_hash: 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.
set_vector_in_hash 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 set_vector_in_hash 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 set_vector_in_hash. 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.
set_vector_in_hash is provided by the Redis MCP Server MCP server (redis/mcp-redis). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 53 Redis MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
53 Redis MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.