start_csv_profiling
Start CSV profiling capture for performance regression analysis.
This record as markdown: /tools/jjpxdev-unreal-mcp/start-csv-profiling.md
What start_csv_profiling does on Unreal
AI agents invoke start_csv_profiling 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 |
|---|---|---|---|
filename | string | — | Output CSV filename (default: auto-generated) |
Parameters from the server's own tool schema.
Why start_csv_profiling is rated High
This tool triggers an external operation (CSV profiling capture) whose effects depend on runtime behavior and what is being profiled. While not destructive or financially harmful, it executes a system operation that could impact engine performance or reveal sensitive performance characteristics.
From the tool's definition Tool name 'start_csv_profiling' and description 'Start CSV profiling capture for performance regression analysis' indicates initiation of a profiling/monitoring operation that captures performance data during Unreal Engine execution.
Risk signalsAccepts file system path (filename)
Attacks that exploit this kind of access
The rule that runs start_csv_profiling 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 start_csv_profiling, this is the rule to start with:
start_csv_profiling 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 start_csv_profiling call is checked against it from then on.
Questions about start_csv_profiling
Start CSV profiling capture for performance regression analysis. 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.
start_csv_profiling accepts 1 parameter: filename. 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 start_csv_profiling: 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.
start_csv_profiling 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 start_csv_profiling 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 start_csv_profiling. 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.
start_csv_profiling 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