Medium Risk

modify_throttle_limit

Dynamically adjust the concurrency limit of an existing throttle without recreating it. Use this to increase/decrease throttle limits based on time of day, system load, or changing business needs. REQUIRES: ruleset_name, throttle_name, new_limit. CHANGES REQUIRE ACTIVATION: Call activate_ruleset ...

How to control modify_throttle_limit ↓

What modify_throttle_limit does on Teradata Workload Management (WLM) MCP Server

AI agents use modify_throttle_limit 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.

Medium Risk

Why modify_throttle_limit needs a policy

This tool modifies the concurrency limit of a throttle rule in Teradata WLM. It is a Write operation because it updates an existing configuration without deleting or irreversibly destroying it.

From the tool's definition 'Dynamically adjust the concurrency limit of an existing throttle without recreating it' — modifies an existing configuration parameter reversibly; 'CHANGES REQUIRE ACTIVATION: Call activate_ruleset after modification' implies the change can be reversed or…

Documented attack patterns abuse exactly the kind of access modify_throttle_limit gives an agent:

How to control modify_throttle_limit

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 modify_throttle_limit:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "modify_throttle_limit": {
      "limits": [
        {
          "counter": "modify_throttle_limit_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

modify_throttle_limit 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.

  1. Create a free account and register Teradata Workload Management (WLM) MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about modify_throttle_limit

What does the modify_throttle_limit tool do? +

Dynamically adjust the concurrency limit of an existing throttle without recreating it. Use this to increase/decrease throttle limits based on time of day, system load, or changing business needs. REQUIRES: ruleset_name, throttle_name, new_limit. CHANGES REQUIRE ACTIVATION: Call activate_ruleset after modification. 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.

How do I enforce a policy on modify_throttle_limit? +

Register the Teradata Workload Management (WLM) MCP Server MCP server in PolicyLayer and add a rule for modify_throttle_limit: 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.

What risk level is modify_throttle_limit? +

modify_throttle_limit is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit modify_throttle_limit? +

Yes. Add a rate_limit block to the modify_throttle_limit 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.

How do I block modify_throttle_limit completely? +

Set action: deny in the PolicyLayer policy for modify_throttle_limit. 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.

What MCP server provides modify_throttle_limit? +

modify_throttle_limit 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.

Enforce policy on every Teradata Workload Management (WLM) MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.