This record as markdown: /tools/jjpxdev-unreal-mcp/generate-collision.md
What generate_collision does on Unreal
AI agents use generate_collision to create or update resources in Unreal, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unreal environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | — | Collision type |
mesh_path | string | Yes | Static mesh asset path |
Parameters from the server's own tool schema.
Why generate_collision is rated Medium
This tool creates or modifies collision geometry for static meshes in Unreal Engine, which is a reversible change to asset properties. It does not execute arbitrary code, delete data, or move funds. While it could impact game performance or behavior if misapplied, the effect is reversible through regeneration or removal of collision data.
From the tool's definition Tool name 'generate_collision' and description 'Generate collision for a static mesh' indicates creation/modification of collision data for game assets. This is a write operation that modifies mesh properties.
Attacks that exploit this kind of access
The rule that runs generate_collision 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 generate_collision, this is the rule to start with:
generate_collision 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Unreal, apply this rule, and every generate_collision call is checked against it from then on.
Questions about generate_collision
Generate collision for a static mesh. It is categorised as a Write tool in the Unreal MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
generate_collision accepts 2 parameters: type, mesh_path. Required: mesh_path. 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 generate_collision: 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.
generate_collision 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 generate_collision 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 generate_collision. 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.
generate_collision 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.
This server
Across the catalogue