list_schedule_presets

List the workspace

SERVERMax MCP Server SOURCEdigital-crew-technologies/max-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/digital-crew-technologies-max-mcp-server/list-schedule-presets.md

WHAT IT DOES

What list_schedule_presets does on Max MCP Server

AI agents call list_schedule_presets to retrieve information from Max MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_schedule_presets is rated Low

The tool retrieves and enumerates schedule presets from the workspace, returning data without any side effects or ability to modify, delete, or execute operations. This is a straightforward read operation. The low severity reflects minimal blast radius—fetching configuration data poses no risk of data loss, financial impact, or system compromise.

From the tool's definition Tool name 'list_schedule_presets' contains 'list', and description states 'List the workspace', both indicating a retrieval operation with no modifications.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_schedule_presets safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Max MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_schedule_presets, this is the rule to start with:

list_schedule_presets Allowed

list_schedule_presets is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Max MCP Server, apply this rule, and every list_schedule_presets call is checked against it from then on.

FAQ

Questions about list_schedule_presets

What does the list_schedule_presets tool do? +

List the workspace. It is categorised as a Read tool in the Max MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_schedule_presets? +

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

What risk level is list_schedule_presets? +

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

Can I rate-limit list_schedule_presets? +

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

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

list_schedule_presets is provided by the Max MCP Server MCP server (digital-crew-technologies/max-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Max MCP Server, and thousands of servers like it.

This server

All 415 Max MCP Server tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_get_delivery_schedule on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →