Display current physical system resources including CPU, memory, and I/O utilization. Use this for capacity planning, health checks, or when investigating performance degradation. Returns metrics for CPU usage, memory consumption, disk I/O, and network activity across the system.
AI agents call show_physical_resources 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 read-only monitoring data without making any modifications, executing code, or causing side effects. It is purely observational, used for capacity planning and health checks. The blast radius of misuse is minimal—an adversary gains visibility into system resources but cannot directly harm systems or data through this tool alone.
From the tool's definition Tool "show_physical_resources" displays/returns metrics for CPU usage, memory consumption, disk I/O, and network activity. The description explicitly states it retrieves current system resource metrics for monitoring and investigation purposes.
Documented attack patterns abuse exactly the kind of access show_physical_resources 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 show_physical_resources:
{
"version": "1",
"default": "deny",
"tools": {
"show_physical_resources": {}
}
}show_physical_resources 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 current physical system resources including CPU, memory, and I/O utilization. Use this for capacity planning, health checks, or when investigating performance degradation. Returns metrics for CPU usage, memory consumption, disk I/O, and network activity across the system. 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 show_physical_resources: 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.
show_physical_resources 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 show_physical_resources 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 show_physical_resources. 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.
show_physical_resources 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.