get_workorder_actuals_vs_planned

Compare estimated vs actual labor hours and cost for a work order — variance analysis.

Server Maximo Enterprise MCP maximo-enterprise-mcp
Category Read
Risk class Low
Parameters 00 required

What get_workorder_actuals_vs_planned does on Maximo Enterprise MCP

AI agents call get_workorder_actuals_vs_planned to retrieve information from Maximo Enterprise MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_workorder_actuals_vs_planned needs a policy

This tool retrieves and analyzes existing work order data (estimated vs actual metrics) for comparison purposes. It performs no state changes, does not execute operations, and does not delete or move resources. The function is purely informational—variance analysis of historical labor and cost data. No side effects on the work order or other system data.

From the tool's definition Tool description states 'Compare estimated vs actual labor hours and cost for a work order — variance analysis.' The verb 'Compare' and the nature of variance analysis indicates data retrieval and reporting only, with no modifications to work orders or…

Questions about get_workorder_actuals_vs_planned

What does the get_workorder_actuals_vs_planned tool do? +

Compare estimated vs actual labor hours and cost for a work order — variance analysis. It is categorised as a Read tool in the Maximo Enterprise MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_workorder_actuals_vs_planned? +

Register the Maximo Enterprise MCP server in PolicyLayer and add a rule for get_workorder_actuals_vs_planned: 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 get_workorder_actuals_vs_planned? +

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

Can I rate-limit get_workorder_actuals_vs_planned? +

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

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

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

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.