Load/reload .rtdq file from disk into Redis cache.
AI agents use load_rtdq_to_redis to create or update resources in Decision Tree MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Decision Tree MCP Server environment.
This tool reads a file from disk and writes/overwrites its contents into Redis cache. It creates or modifies data in Redis (potentially overwriting existing cached decision tree data), which is a reversible write operation. It does not delete data permanently, execute arbitrary code, or involve financial transactions.
From the tool's definition Load/reload .rtdq file from disk into Redis cache
Attacks that exploit this kind of access
Load/reload .rtdq file from disk into Redis cache. It is categorised as a Write tool in the Decision Tree MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Decision Tree MCP Server MCP server in PolicyLayer and add a rule for load_rtdq_to_redis: 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 Decision Tree MCP Server. Nothing to install.
load_rtdq_to_redis 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 load_rtdq_to_redis 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 load_rtdq_to_redis. 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.
load_rtdq_to_redis is provided by the Decision Tree MCP Server MCP server (psikosen/dt_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 →