Create a Redis 8 vector similarity index using HNSW on a Redis hash. This function sets up a Redis index for approximate nearest neighbor (ANN) search using the HNSW algorithm and float32 vector embeddings. Args: index_name: The name of the Redis index to create. Unless specifically required, use...
AI agents use create_vector_index_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 a new index in Redis, which is a reversible modification operation. It does not execute arbitrary code, delete data irreversibly, nor move money. While it modifies the database structure, Redis indexes can be deleted or recreated, making this a Write operation.
From the tool's definition The tool description explicitly states it 'Create[s] a Redis 8 vector similarity index', which is a data creation operation. The function parameters include 'index_name', 'prefix', and 'vector_field' used to set up and configure a new index structure.
Documented attack patterns abuse exactly the kind of access create_vector_index_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 create_vector_index_hash:
{
"version": "1",
"default": "deny",
"tools": {
"create_vector_index_hash": {
"limits": [
{
"counter": "create_vector_index_hash_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_vector_index_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.
Create a Redis 8 vector similarity index using HNSW on a Redis hash. This function sets up a Redis index for approximate nearest neighbor (ANN) search using the HNSW algorithm and float32 vector embeddings. Args: index_name: The name of the Redis index to create. Unless specifically required, use the default name for the index. prefix: The key prefix used to identify documents to index (e.g., 'doc:'). Unless specifically required, use the default prefix. vector_field: The name of the vector field to be indexed for similarity search. Unless specifically required, use the default field name dim: The dimensionality of the vectors stored under the vector_field. distance_metric: The distance function to use (e.g., 'COSINE', 'L2', 'IP'). Returns: A string indicating whether the index was created successfully or an error message. 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 create_vector_index_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.
create_vector_index_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 create_vector_index_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 create_vector_index_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.
create_vector_index_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.