performance_stop_trace

Stop the active trace recording and optionally load it for analysis.

SERVERUnreal-MCP SOURCEaadeshrao123/unreal-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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…

Questions about performance_stop_trace

What does the performance_stop_trace tool do? +

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.

How do I enforce a policy on performance_stop_trace? +

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.

What risk level is performance_stop_trace? +

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

Can I rate-limit performance_stop_trace? +

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.

How do I block performance_stop_trace completely? +

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.

What MCP server provides performance_stop_trace? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Unreal's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.