This record as markdown: /tools/namastexlabs-automagik-tools/list-schedules.md
What list_schedules does on Automagik Tools
AI agents call list_schedules to retrieve information from Automagik Tools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_schedules is rated Low
This tool retrieves and displays schedule information without side effects. It is a read-only operation that queries existing data. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—an attacker would gain visibility into schedules but could not alter system state or trigger actions.
From the tool's definition Tool name 'list_schedules' and description 'List all active schedules' indicate a query/retrieval operation with no modification, deletion, or execution of external actions.
Attacks that exploit this kind of access
The rule that runs list_schedules safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Automagik Tools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_schedules, this is the rule to start with:
list_schedules is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Automagik Tools, apply this rule, and every list_schedules call is checked against it from then on.
Questions about list_schedules
List all active schedules. It is categorised as a Read tool in the Automagik Tools MCP Server, which means it retrieves data without modifying state.
Register the Automagik Tools MCP server in PolicyLayer and add a rule for list_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 Automagik Tools. Nothing to install.
list_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_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_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_schedules is provided by the Automagik Tools MCP server (namastexlabs/automagik-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Automagik Tools, and thousands of servers like it.
This server
Across the catalogue