performance
Performance & Crash Monitor. snapshot: collect current metrics. baseline: save metrics for comparison. compare: PASS/FAIL against baseline. monitor: continuous sampling over duration. crashes: query crash/ANR logs. framestats: GPU frame rendering statistics with jank rate and percentiles (Android...
This record as markdown: /tools/alexgladkov-claude-in-mobile/performance.md
What performance does on Claude Mobile
AI agents invoke performance to trigger actions in Claude Mobile. 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 is rated High
This tool executes monitoring and diagnostic operations on mobile devices rather than passively retrieving static data. The 'monitor' function with configurable duration and the ability to query system logs represent executable operations that trigger active processes. It is not purely Read (which would be passive data retrieval) because it initiates sampling and monitoring processes.
From the tool's definition The tool performs monitoring and sampling operations (snapshot, baseline, compare, monitor, crashes, framestats) that trigger active data collection and analysis processes on the mobile device.
Attacks that exploit this kind of access
The rule that runs performance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Mobile, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For performance, this is the rule to start with:
performance 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 Claude Mobile, apply this rule, and every performance call is checked against it from then on.
Questions about performance
Performance & Crash Monitor. snapshot: collect current metrics. baseline: save metrics for comparison. compare: PASS/FAIL against baseline. monitor: continuous sampling over duration. crashes: query crash/ANR logs. framestats: GPU frame rendering statistics with jank rate and percentiles (Android only). It is categorised as a Execute tool in the Claude Mobile MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Mobile MCP server in PolicyLayer and add a rule for performance: 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 Claude Mobile. Nothing to install.
performance 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 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. 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 is provided by the Claude Mobile MCP server (alexgladkov/claude-in-mobile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude Mobile, and thousands of servers like it.
Across the catalogue