identify_blocking

ServerTeradata Workload Management (WLM) MCP Server
CategoryRead

WHAT IT DOES

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

AI agents call identify_blocking 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.

THE RISK

Low Risk

Why identify_blocking needs a policy

This tool queries and retrieves monitoring data about session blocking relationships. It performs read-only diagnostics to help understand query execution states. There is no mention of modifying configurations, executing commands, deleting data, or affecting financial systems. The 'identify' verb and 'Returns information' phrase confirm this is a passive monitoring/diagnostic read operation.

From the tool's definition Tool description states it 'Identify sessions' and 'Returns information about blocking sessions' - a pure retrieval operation with no modifications or side effects.

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

POLICY

How to control identify_blocking

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "identify_blocking": {}
  }
}

identify_blocking is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Teradata Workload Management (WLM) MCP Server tools

Destructive abort_delayed_request CANCEL and permanently abort a delayed query in the queue. The query will not execute and Destructive delete_filter PERMANENTLY DELETE a filter rule. REQUIRES: ruleset_name, filter_name. CHANGES REQUIRE ACT Destructive delete_throttle PERMANENTLY DELETE a throttle rule from the ruleset configuration. REQUIRES: ruleset_name, Destructive abort_sessions_user TERMINATES all active sessions for a specified user. This immediately kills all running qu Execute release_delay_queue Release a delayed query from the queue, allowing it to execute immediately. Use this to ma Execute activate_ruleset ACTIVATE a ruleset to apply ALL pending configuration changes to the live system. MUST BE Write add_classification_to_rule Add classification criteria to an existing rule (throttle, filter, or workload). Classific Write add_subcriteria_to_target Add sub-criteria to a target classification for advanced rule targeting. Sub-criteria type

All 41 Teradata Workload Management (WLM) MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about identify_blocking

What does the identify_blocking tool do? +

Identify sessions that are blocking other sessions from executing. Use this when queries appear stuck or when investigating why queries are delayed. Returns information about blocking sessions (blockers) and blocked sessions (waiters), including session IDs and users involved. 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.

How do I enforce a policy on identify_blocking? +

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

identify_blocking is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit identify_blocking? +

Yes. Add a rate_limit block to the identify_blocking 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 identify_blocking completely? +

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

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

CHECK YOUR STACK →

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.