Record an app once with a profiling preset and return one combined report. Prefer attach-by-PID for already-running apps; use launch mode only for startup/cold-launch profiling.
AI agents invoke profile_running_app to trigger actions in XcodeTraceMCP. 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.
This tool attaches to or launches processes and records profiling data using Xcode Instruments (xctrace). It triggers external operations on live processes (attach by PID or launch), which constitutes Execute-level action. Misuse could interfere with running applications, cause performance degradation, or expose sensitive runtime data.
From the tool's definition 'Record an app once with a profiling preset' and 'attach-by-PID for already-running apps; use launch mode only for startup/cold-launch profiling' — the tool actively records/profiles a running process or launches an app
Documented attack patterns abuse exactly the kind of access profile_running_app gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and XcodeTraceMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for profile_running_app:
{
"version": "1",
"default": "deny",
"tools": {
"profile_running_app": {
"limits": [
{
"counter": "profile_running_app_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}profile_running_app 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.
Free to start. No card required.
Record an app once with a profiling preset and return one combined report. Prefer attach-by-PID for already-running apps; use launch mode only for startup/cold-launch profiling. It is categorised as a Execute tool in the XcodeTraceMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the XcodeTrace MCP server in PolicyLayer and add a rule for profile_running_app: 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 XcodeTraceMCP. Nothing to install.
profile_running_app 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 profile_running_app 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 profile_running_app. 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.
profile_running_app is provided by the XcodeTrace MCP server (jamesrochabrun/xcodetracemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from XcodeTraceMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 XcodeTraceMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.