Initializes a new Swift package and returns structured result with created files.
AI agents use package-init to create or update resources in Make — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Make environment.
This tool creates new files/directories for a Swift package. It's a Write operation (creates data reversibly/traceably). It doesn't execute arbitrary code or delete data. Severity is medium because initializing a package creates files on the filesystem, but these are easily removed and don't have wide blast radius.
From the tool's definition Initializes a new Swift package and returns structured result with created files
Documented attack patterns abuse exactly the kind of access package-init gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Make, and nothing reaches the server without passing your rules. This is the rule we recommend for package-init:
{
"version": "1",
"default": "deny",
"tools": {
"package-init": {
"limits": [
{
"counter": "package-init_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Initializes a new Swift package and returns structured result with created files. It is categorised as a Write tool in the Make MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Make 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 Make. Nothing to install.
package-init is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
package-init is provided by the Make MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Make, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
202 Make tools catalogued and risk-classified — across an index of 43,000+ MCP servers.