List execution schedules — cron-based triggers that run tasks or workflows automatically.
AI agents call list_execute_schedules to retrieve information from Morpheus 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 existing execution schedules without altering them. Listing schedules is a non-destructive information retrieval operation. The severity is low because misuse would only expose schedule metadata, not cause infrastructure changes. The confidence is high given the explicit 'list' verb in both name and description.
From the tool's definition Tool name 'list_execute_schedules' and description 'List execution schedules' indicate a read/query operation. The verb 'list' is a passive retrieval action with no side effects.
Attacks that exploit this kind of access
List execution schedules — cron-based triggers that run tasks or workflows automatically. It is categorised as a Read tool in the Morpheus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Morpheus MCP Server MCP server in PolicyLayer and add a rule for list_execute_schedules: 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 Morpheus MCP Server. Nothing to install.
list_execute_schedules 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 list_execute_schedules 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 list_execute_schedules. 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.
list_execute_schedules is provided by the Morpheus MCP Server MCP server (nixndme/morpheus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →