nanobot_schedule_cron · VibeServe MCP: Risk & Policy

WHAT IT DOES

What nanobot_schedule_cron does on VibeServe

AI agents invoke nanobot_schedule_cron to trigger actions in VibeServe. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why nanobot_schedule_cron needs a policy

Scheduling a cron job triggers recurring execution of automated tasks. This has Execute-level risk because it sets up persistent, repeated operations that could run arbitrary workloads on a schedule. Misuse could cause repeated execution of unintended actions at scale, giving it a high severity blast radius.

From the tool's definition Register a cron job in nanobot

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

nanobot_schedule_cron Rate-limited

nanobot_schedule_cron stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "nanobot_schedule_cron": {
      "limits": [
        {
          "counter": "nanobot_schedule_cron_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about nanobot_schedule_cron

What does the nanobot_schedule_cron tool do? +

Register a cron job in nanobot. It is categorised as a Execute tool in the VibeServe MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on nanobot_schedule_cron? +

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

What risk level is nanobot_schedule_cron? +

nanobot_schedule_cron is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit nanobot_schedule_cron? +

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

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

nanobot_schedule_cron is provided by the VibeServe MCP server (ncsound919/vibeserve). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.