package-init

Initializes a new Swift package and returns structured result with created files.

SERVERBuild SOURCEDave-London/Pare

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-build/package-init.md

WHAT IT DOES

What package-init does on Build

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

RISK

Why package-init is rated Medium

This tool creates new files and directory structures for a Swift package. It is a Write operation (creates data reversibly) with medium severity since it writes to the filesystem but does not delete or overwrite existing data, execute arbitrary code, or involve financial operations.

From the tool's definition Initializes a new Swift package and returns structured result with created files

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs package-init safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Build, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For package-init, this is the rule to start with:

package-init Rate-limited

package-init 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": {
    "package-init": {
      "limits": [
        {
          "counter": "package-init_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Build, apply this rule, and every package-init call is checked against it from then on.

FAQ

Questions about package-init

What does the package-init tool do? +

Initializes a new Swift package and returns structured result with created files. It is categorised as a Write tool in the Build MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on package-init? +

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

What risk level is package-init? +

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

Can I rate-limit package-init? +

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

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

package-init is provided by the Build MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Build, and thousands of servers like it.

This server

All 202 Build tools →

Across the catalogue

create_package_backup on Android Forensics ADB MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →