Display details for a specific type of delay queue. Valid types:
AI agents call display_delay_queue to retrieve information from Teradata Workload Management (WLM) MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about delay queues without making any changes to the system. It is a read-only operation with minimal blast radius if misused by an AI agent, as it only exposes existing queue status information.
From the tool's definition Tool name 'display_delay_queue' and description indicate it 'Display details for a specific type of delay queue' - a retrieval/query operation with no modification, creation, or deletion of data.
Documented attack patterns abuse exactly the kind of access display_delay_queue gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Teradata Workload Management (WLM) MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for display_delay_queue:
{
"version": "1",
"default": "deny",
"tools": {
"display_delay_queue": {}
}
} display_delay_queue is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
All 41 Teradata Workload Management (WLM) MCP Server tools →
Display details for a specific type of delay queue. Valid types:. It is categorised as a Read tool in the Teradata Workload Management (WLM) MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Teradata Workload Management (WLM) MCP Server MCP server in PolicyLayer and add a rule for display_delay_queue: 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 Teradata Workload Management (WLM) MCP Server. Nothing to install.
display_delay_queue 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 display_delay_queue 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 display_delay_queue. 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.
display_delay_queue is provided by the Teradata Workload Management (WLM) MCP Server MCP server (teradata-labs/mcp-server-teradata-wlm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Teradata Workload Management (WLM) MCP Server, 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.
41 Teradata Workload Management (WLM) MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.