Disable (deactivate) a throttle rule without deleting it. REQUIRES: ruleset_name, throttle_name. CHANGES REQUIRE ACTIVATION.
AI agents use disable_throttle 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.
Disabling a throttle rule modifies workload management settings in a way that can be undone (re-enabled later), making this a Write operation rather than Destructive. The tool does not delete data or create irreversible changes.
From the tool's definition Tool description states it will "disable (deactivate) a throttle rule" and explicitly notes "CHANGES REQUIRE ACTIVATION," indicating the action modifies system configuration state reversibly without deletion.
Documented attack patterns abuse exactly the kind of access disable_throttle 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 disable_throttle:
{
"version": "1",
"default": "deny",
"tools": {
"disable_throttle": {
"limits": [
{
"counter": "disable_throttle_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} disable_throttle 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 →
Disable (deactivate) a throttle rule without deleting it. REQUIRES: ruleset_name, throttle_name. CHANGES REQUIRE ACTIVATION. 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 disable_throttle: 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.
disable_throttle 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 disable_throttle 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 disable_throttle. 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.
disable_throttle 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.