vibekit_create_schedule · Vibekit MCP: Risk & Policy

WHAT IT DOES

What vibekit_create_schedule does on Vibekit

AI agents use vibekit_create_schedule to create or update resources in Vibekit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vibekit environment.

WHY IT NEEDS A POLICY

Why vibekit_create_schedule needs a policy

This tool creates a new recurring schedule, which is a Write operation — it creates a persistent configuration/schedule object. It does not delete or irreversibly modify data, execute arbitrary code directly, or involve financial transactions. The medium severity reflects that a misused schedule could repeatedly trigger coding tasks on GitHub repositories.

From the tool's definition Create a recurring coding task schedule (GitHub-based, not app-agent based)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vibekit_create_schedule Rate-limited

vibekit_create_schedule stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vibekit_create_schedule": {
      "limits": [
        {
          "counter": "vibekit_create_schedule_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Vibekit, so you can run agents against it safely.

FAQ

Questions about vibekit_create_schedule

What does the vibekit_create_schedule tool do? +

Create a recurring coding task schedule (GitHub-based, not app-agent based). It is categorised as a Write tool in the Vibekit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on vibekit_create_schedule? +

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

What risk level is vibekit_create_schedule? +

vibekit_create_schedule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit vibekit_create_schedule? +

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

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

What MCP server provides vibekit_create_schedule? +

vibekit_create_schedule is provided by the Vibekit MCP server (vibekit-apps/vibekit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.