ops_redis_read
读取已保存 Redis 连接的单个键，无需额外板块授权。支持 GET、TYPE、TTL、PTTL、EXISTS、STRLEN、HLEN、LLEN、SCARD、ZCARD、HGET、HEXISTS、SISMEMBER、ZSCORE、GETRANGE。所有参数独立传递，不能使用脚本、管理命令或跨逻辑库；返回有界且可能截断。${UNTRUSTED_EVIDENCE}
This record as markdown: /tools/dutydeck/ops-redis-read.md
What ops_redis_read does on DutyDeck
AI agents call ops_redis_read to retrieve information from DutyDeck without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why ops_redis_read is rated Low
Even though ops_redis_read only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs ops_redis_read safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DutyDeck, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ops_redis_read, this is the rule to start with:
ops_redis_read is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect DutyDeck, apply this rule, and every ops_redis_read call is checked against it from then on.
Questions about ops_redis_read
读取已保存 Redis 连接的单个键，无需额外板块授权。支持 GET、TYPE、TTL、PTTL、EXISTS、STRLEN、HLEN、LLEN、SCARD、ZCARD、HGET、HEXISTS、SISMEMBER、ZSCORE、GETRANGE。所有参数独立传递，不能使用脚本、管理命令或跨逻辑库；返回有界且可能截断。${UNTRUSTED_EVIDENCE}. It is categorised as a Read tool in the DutyDeck MCP Server, which means it retrieves data without modifying state.
Register the DutyDeck MCP server in PolicyLayer and add a rule for ops_redis_read: 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 DutyDeck. Nothing to install.
ops_redis_read is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ops_redis_read 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 ops_redis_read. 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.
ops_redis_read is provided by the DutyDeck MCP server (taokoplay/DutyDeck). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DutyDeck, and thousands of servers like it.
This server
Across the catalogue