get_schedule_calendar

Return scheduled work orders within a date window grouped by date or as a flat list.

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

What get_schedule_calendar does on Maximo Enterprise MCP

AI agents call get_schedule_calendar 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_schedule_calendar needs a policy

This is a pure data retrieval operation. It queries and returns scheduled work orders filtered by a date range, presenting them in either grouped or flat format. There are no side effects, no data modification, no code execution, and no destructive operations. The tool serves an informational/planning purpose only, making it a Read category risk with low severity.

From the tool's definition Tool name and description: 'Return scheduled work orders within a date window' - retrieves/queries existing schedule data with no modification, creation, deletion, or execution capabilities.

Questions about get_schedule_calendar

What does the get_schedule_calendar tool do? +

Return scheduled work orders within a date window grouped by date or as a flat list. 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_schedule_calendar? +

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

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

Can I rate-limit get_schedule_calendar? +

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

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

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