Display the query band settings for a specific session. Use this to see how a particular session is tagged, verify application is setting query bands correctly, or troubleshoot why a query is being classified into the wrong workload. Requires sessionNo parameter. Returns all query band name-value...
AI agents call monitor_session_query_band 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 configuration and diagnostic information about a specific session's query band settings. It has no side effects, does not modify any state, and serves purely for monitoring and troubleshooting purposes. The action is inherently safe and fits the Read category profile of querying data for inspection.
From the tool's definition Tool displays/returns query band settings for a session without modifying any data. Description uses 'Display', 'see', and 'verify' indicating read-only operations. Returns data without creating, modifying, or deleting anything.
Documented attack patterns abuse exactly the kind of access monitor_session_query_band 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 monitor_session_query_band:
{
"version": "1",
"default": "deny",
"tools": {
"monitor_session_query_band": {}
}
} monitor_session_query_band 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 the query band settings for a specific session. Use this to see how a particular session is tagged, verify application is setting query bands correctly, or troubleshoot why a query is being classified into the wrong workload. Requires sessionNo parameter. Returns all query band name-value pairs for that session. 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 monitor_session_query_band: 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.
monitor_session_query_band 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 monitor_session_query_band 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 monitor_session_query_band. 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.
monitor_session_query_band 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.