Use this when the user wants to automate a task to run repeatedly on a schedule. Perfect for weekly reports, daily social media posts, monthly analytics summaries, regular backups, or scheduled content campaigns. Supports flexible schedules like "every Monday at 9am", "daily at noon", or "first d...
Bulk/mass operation — affects multiple targets
Part of the Athenic MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use schedule_recurring_task to create or modify resources in Athenic. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call schedule_recurring_task repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Athenic.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
schedule_recurring_task:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Athenic policy for all 5 tools.
Agents calling write-class tools like schedule_recurring_task have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Use this when the user wants to automate a task to run repeatedly on a schedule. Perfect for weekly reports, daily social media posts, monthly analytics summaries, regular backups, or scheduled content campaigns. Supports flexible schedules like "every Monday at 9am", "daily at noon", or "first day of each month". Tasks run automatically without user intervention.. It is categorised as a Write tool in the Athenic MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for schedule_recurring_task. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Athenic MCP server.
schedule_recurring_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the schedule_recurring_task rule in your Intercept 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 Intercept policy for schedule_recurring_task. 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.
schedule_recurring_task is provided by the Athenic MCP server (maxbeech/athenic). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept