generate_pm_workorders · Maximo Enterprise MCP

WHAT IT DOES

What generate_pm_workorders does on Maximo Enterprise MCP

AI agents invoke generate_pm_workorders to trigger actions in Maximo Enterprise MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why generate_pm_workorders needs a policy

This tool triggers an automated process that generates work orders in Maximo, which is an external operation with real system-side effects (creating records). While it creates data (Write-like), the 'trigger' aspect of firing an automated generation process across potentially many assets/schedules makes it Execute.

From the tool's definition 'Trigger PM work order generation' — triggers an external operation that creates multiple work orders in the system based on scheduled maintenance plans

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_pm_workorders Rate-limited

generate_pm_workorders stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_pm_workorders": {
      "limits": [
        {
          "counter": "generate_pm_workorders_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Maximo Enterprise MCP, so you can run agents against it safely.

FAQ

Questions about generate_pm_workorders

What does the generate_pm_workorders tool do? +

Trigger PM work order generation for upcoming scheduled maintenance. Requires supervisor role. It is categorised as a Execute tool in the Maximo Enterprise MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on generate_pm_workorders? +

Register the Maximo Enterprise MCP server in PolicyLayer and add a rule for generate_pm_workorders: 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 Maximo Enterprise MCP. Nothing to install.

What risk level is generate_pm_workorders? +

generate_pm_workorders is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit generate_pm_workorders? +

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

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

generate_pm_workorders is provided by the Maximo Enterprise MCP server (maximo-enterprise-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.