AI agents use redis_connect to create or update resources in Db — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Db environment.
Establishing a database connection is not a pure read — it creates a persistent session/resource and may authenticate, allocate server-side state, or open a socket. It is reversible (connections can be closed), so Write is the most appropriate category. It is not destructive, financial, or an execution of arbitrary code.
From the tool's definition 连接到 Redis 数据库 (Connect to Redis database)
Documented attack patterns abuse exactly the kind of access redis_connect gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Db, and nothing reaches the server without passing your rules. This is the rule we recommend for redis_connect:
{
"version": "1",
"default": "deny",
"tools": {
"redis_connect": {
"limits": [
{
"counter": "redis_connect_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}redis_connect 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.
连接到 Redis 数据库. It is categorised as a Write tool in the Db MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Db MCP server in PolicyLayer and add a rule for redis_connect: 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 Db. Nothing to install.
redis_connect 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 redis_connect 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 redis_connect. 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.
redis_connect is provided by the Db MCP server (wannanbigpig/db-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Db, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
34 Db tools catalogued and risk-classified — across an index of 43,000+ MCP servers.