performance_stop_trace
Stop the active trace recording and optionally load it for analysis.
This record as markdown: /tools/aadeshrao123-unreal-mcp/performance-stop-trace.md
What performance_stop_trace does on Unreal-MCP
AI agents invoke performance_stop_trace to trigger actions in Unreal-MCP. 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 performance_stop_trace is rated High
This is Execute rather than Write because it terminates an active monitoring operation and may trigger subsequent analysis workflows, both of which are external operations with side effects that depend on runtime state. It's not Read-only (it modifies trace state), not Destructive (the trace data is preserved), and not Financial.
From the tool's definition The tool 'performance_stop_trace' stops an active trace recording and loads it for analysis. This triggers an external operation (halting an in-progress profiling/tracing session) whose effects depend on what trace was active and whether it's loaded for…
Attacks that exploit this kind of access
The rule that runs performance_stop_trace safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unreal-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For performance_stop_trace, this is the rule to start with:
performance_stop_trace 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-MCP, apply this rule, and every performance_stop_trace call is checked against it from then on.
Questions about performance_stop_trace
Stop the active trace recording and optionally load it for analysis. It is categorised as a Execute tool in the Unreal-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Unreal MCP server in PolicyLayer and add a rule for performance_stop_trace: 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-MCP. Nothing to install.
performance_stop_trace 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 performance_stop_trace 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 performance_stop_trace. 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.
performance_stop_trace is provided by the Unreal MCP server (aadeshrao123/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