package_project · Unreal MCP: Risk & Policy

WHAT IT DOES

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.

WHY IT NEEDS A POLICY

Why package_project needs a policy

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

Recommended rule Ready

Verdict

package_project Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "package_project": {
      "limits": [
        {
          "counter": "package_project_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 Unreal, so you can run agents against it safely.

FAQ

Questions about package_project

What does the package_project tool do? +

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.

How do I enforce a policy on package_project? +

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.

What risk level is package_project? +

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

Can I rate-limit package_project? +

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.

How do I block package_project completely? +

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.

What MCP server provides package_project? +

package_project is provided by the Unreal MCP server (sam-david/unreal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.