nanobot_run_skill · VibeServe MCP: Risk & Policy

WHAT IT DOES

What nanobot_run_skill does on VibeServe

AI agents invoke nanobot_run_skill 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_run_skill needs a policy

This tool permits execution of named skills without specifying what those skills do. An AI agent could invoke arbitrary nanobots with unpredictable side effects (generating code, modifying state, calling external APIs, etc.). The blast radius depends on what skills are available and whether they are constrained.

From the tool's definition Tool name 'nanobot_run_skill' with description 'Execute a nanobot skill by name' indicates arbitrary execution of skills by name parameter.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

nanobot_run_skill Rate-limited

nanobot_run_skill 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_run_skill": {
      "limits": [
        {
          "counter": "nanobot_run_skill_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_run_skill

What does the nanobot_run_skill tool do? +

Execute a nanobot skill by name. 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_run_skill? +

Register the VibeServe MCP server in PolicyLayer and add a rule for nanobot_run_skill: 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_run_skill? +

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

Can I rate-limit nanobot_run_skill? +

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

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

nanobot_run_skill 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.