Add classification criteria to an existing rule (throttle, filter, or workload). Classification types: USER, APPL, TABLE, QUERYBAND, STMT, CLIENTADDR, etc. REQUIRES: ruleset_name, rule_name, description, classification_type, classification_value. OPTIONAL: operator (
AI agents use add_classification_to_rule to create or update resources in Teradata Workload Management (WLM) MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Teradata Workload Management (WLM) MCP Server environment.
This tool creates or modifies rule configurations reversibly. While it affects system behavior through workload management rules, it does not execute arbitrary code, delete data, move money, or trigger irreversible changes. The modification of workload rules could impact system performance and resource allocation, warranting high severity, but the action itself is reversible (criteria can be removed/modified).
From the tool's definition Tool adds classification criteria to existing rules, modifying rule configurations. The description explicitly states it adds criteria to rules, which are configuration objects that control workload management behavior.
Documented attack patterns abuse exactly the kind of access add_classification_to_rule 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 add_classification_to_rule:
{
"version": "1",
"default": "deny",
"tools": {
"add_classification_to_rule": {
"limits": [
{
"counter": "add_classification_to_rule_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_classification_to_rule 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.
All 41 Teradata Workload Management (WLM) MCP Server tools →
Add classification criteria to an existing rule (throttle, filter, or workload). Classification types: USER, APPL, TABLE, QUERYBAND, STMT, CLIENTADDR, etc. REQUIRES: ruleset_name, rule_name, description, classification_type, classification_value. OPTIONAL: operator (. It is categorised as a Write tool in the Teradata Workload Management (WLM) MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Teradata Workload Management (WLM) MCP Server MCP server in PolicyLayer and add a rule for add_classification_to_rule: 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.
add_classification_to_rule 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 add_classification_to_rule 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 add_classification_to_rule. 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.
add_classification_to_rule 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.