Manage scheduled recurring runs for recipes. Each recipe can have one schedule that runs indefinitely. Only recurring schedules are supported. Schedules can be paused and resumed anytime. Use this tool when user wants to: - Schedule a recipe to run periodically - Pause or resume a re...
Bulk/mass operation — affects multiple targets
Part of the Rube MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use RUBE_MANAGE_RECIPE_SCHEDULE to create or modify resources in Rube. 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 RUBE_MANAGE_RECIPE_SCHEDULE 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 Rube.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
RUBE_MANAGE_RECIPE_SCHEDULE:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Rube policy for all 11 tools.
Agents calling write-class tools like RUBE_MANAGE_RECIPE_SCHEDULE 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.
Manage scheduled recurring runs for recipes. Each recipe can have one schedule that runs indefinitely. Only recurring schedules are supported. Schedules can be paused and resumed anytime. Use this tool when user wants to: - Schedule a recipe to run periodically - Pause or resume a recipe schedule - Update schedule timing or parameters - Delete a recipe schedule - Check current schedule status If vibeApiId is already in context, use it directly. Otherwise, use RUBE_FIND_RECIPES first. Behavior: - If no schedule exists for the recipe, one is created - If schedule exists, it is updated - delete=true takes priority over all other actions - schedule and params can be updated independently Cron format: "minute hour day month weekday" Examples: - "every weekday at 9am" → "0 9 * * 1-5" - "every Monday at 8am" → "0 8 * * 1" - "daily at midnight" → "0 0 * * *" - "every hour" → "0 * * * *" - "1st of every month at 9am" → "0 9 1 * *" . It is categorised as a Write tool in the Rube 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 RUBE_MANAGE_RECIPE_SCHEDULE. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Rube MCP server.
RUBE_MANAGE_RECIPE_SCHEDULE 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 RUBE_MANAGE_RECIPE_SCHEDULE 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 RUBE_MANAGE_RECIPE_SCHEDULE. 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.
RUBE_MANAGE_RECIPE_SCHEDULE is provided by the Rube MCP server (Composio/Rube). 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