cook_content · Unreal MCP: Risk & Policy

WHAT IT DOES

What cook_content does on Unreal

AI agents invoke cook_content 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 cook_content needs a policy

The cook_content tool executes a content cooking pipeline in Unreal Engine, which is an external operation that transforms and processes game assets. This is an Execute category tool because it runs a complex build operation with side effects (asset conversion, file generation, potential errors). While not destructive (original assets remain), it triggers significant external processing.

From the tool's definition 'Cook content only (no C++ build). Converts assets to platform-specific format.' - this runs a build pipeline operation that processes and transforms assets, triggering external compilation/conversion operations whose effects depend on which assets are…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cook_content Rate-limited

cook_content 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": {
    "cook_content": {
      "limits": [
        {
          "counter": "cook_content_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 cook_content

What does the cook_content tool do? +

Cook content only (no C++ build). Converts assets to platform-specific format. 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 cook_content? +

Register the Unreal MCP server in PolicyLayer and add a rule for cook_content: 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 cook_content? +

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

Can I rate-limit cook_content? +

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

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

cook_content 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.