cap_build · Sflight MCP: Risk & Policy

WHAT IT DOES

What cap_build does on Sflight

AI agents invoke cap_build to trigger actions in Sflight. 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 cap_build needs a policy

This tool triggers a CDS (Core Data Services) build process that compiles models into deployment-ready artifacts. This is an Execute action because it runs an external operation (build compilation) whose effects depend on the CDS models and configuration provided. While not destructive in itself, a malicious build could generate corrupted or malicious artifacts for deployment.

From the tool's definition 'Run CDS build (production or development). Compiles CDS models to deployment artifacts' — the tool executes a build process that generates deployment artifacts, which is a code compilation and transformation operation with external effects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cap_build Rate-limited

cap_build 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": {
    "cap_build": {
      "limits": [
        {
          "counter": "cap_build_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 Sflight, so you can run agents against it safely.

FAQ

Questions about cap_build

What does the cap_build tool do? +

Run CDS build (production or development). Compiles CDS models to deployment artifacts. It is categorised as a Execute tool in the Sflight MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on cap_build? +

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

What risk level is cap_build? +

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

Can I rate-limit cap_build? +

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

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

cap_build is provided by the Sflight MCP server (mindsetconsulting/sflight-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.