stop_csv_profiling
Stop CSV profiling capture and save results.
This record as markdown: /tools/jjpxdev-unreal-mcp/stop-csv-profiling.md
What stop_csv_profiling does on Unreal
AI agents use stop_csv_profiling 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.
Why stop_csv_profiling is rated Medium
This tool stops an ongoing profiling session and saves the captured data to a file. It writes/persists results to disk. It is not purely read (it creates output files) and not destructive (it saves rather than deletes). 'Save results' indicates a write operation with moderate blast radius if misused during an active profiling session.
From the tool's definition Stop CSV profiling capture and save results
Attacks that exploit this kind of access
The rule that runs stop_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 stop_csv_profiling, this is the rule to start with:
stop_csv_profiling 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 stop_csv_profiling call is checked against it from then on.
Questions about stop_csv_profiling
Stop CSV profiling capture and save results. 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.
Register the Unreal MCP server in PolicyLayer and add a rule for stop_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.
stop_csv_profiling 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 stop_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 stop_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.
stop_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.
This server
Across the catalogue