package_project
Package the project for distribution. Runs build + cook + stage + package.
This record as markdown: /tools/jjpxdev-unreal-mcp/package-project.md
What package_project does on Unreal
AI agents invoke package_project to trigger actions in Unreal. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
platform | string | — | Target platform |
compressed | boolean | — | Compress pak files |
configuration | object | — | Build configuration (typically Shipping for distribution) |
Parameters from the server's own tool schema.
Why package_project is rated High
This tool orchestrates a complex build pipeline (build, cook, stage, package) that compiles code, processes assets, and generates distributable binaries. While not immediately destructive or financial, it is clearly Execute-category because it triggers external operations whose effects depend on project state and configuration, and could consume significant resources or produce unintended outputs if misused by an…
From the tool's definition 'Package the project for distribution. Runs build + cook + stage + package.' - describes execution of a multi-stage build and packaging pipeline with external operations and side effects that transform project artifacts.
Attacks that exploit this kind of access
The rule that runs package_project safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unreal, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For package_project, this is the rule to start with:
package_project 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Unreal, apply this rule, and every package_project call is checked against it from then on.
Questions about package_project
Package the project for distribution. Runs build + cook + stage + package. It is categorised as a Execute tool in the Unreal MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
package_project accepts 3 parameters: platform, compressed, configuration. The full parameter table on this page comes from the server's own tool schema.
Register the Unreal MCP server in PolicyLayer and add a rule for package_project: 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 Unreal. Nothing to install.
package_project is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the package_project 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_project. 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_project is provided by the Unreal MCP server (@jjpxdev/unreal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Unreal, and thousands of servers like it.
Across the catalogue