performance_snapshot

Collect current performance metrics: memory, CPU, FPS, battery, crash count. Returns formatted report.

SERVERClaude Mobile SOURCEalexgladkov/claude-in-mobile

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/alexgladkov-claude-in-mobile/performance-snapshot.md

WHAT IT DOES

What performance_snapshot does on Claude Mobile

AI agents call performance_snapshot to retrieve information from Claude Mobile without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why performance_snapshot is rated Low

The tool only reads and returns device performance metrics (memory, CPU, FPS, battery, crash count) without modifying any state, executing commands, or causing side effects. It is a pure data collection/query operation.

From the tool's definition Collect current performance metrics: memory, CPU, FPS, battery, crash count. Returns formatted report.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs performance_snapshot 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_snapshot, this is the rule to start with:

performance_snapshot Allowed

performance_snapshot is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "performance_snapshot": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Mobile, apply this rule, and every performance_snapshot call is checked against it from then on.

FAQ

Questions about performance_snapshot

What does the performance_snapshot tool do? +

Collect current performance metrics: memory, CPU, FPS, battery, crash count. Returns formatted report. It is categorised as a Read tool in the Claude Mobile MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on performance_snapshot? +

Register the Claude Mobile MCP server in PolicyLayer and add a rule for performance_snapshot: 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.

What risk level is performance_snapshot? +

performance_snapshot is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit performance_snapshot? +

Yes. Add a rate_limit block to the performance_snapshot 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_snapshot completely? +

Set action: deny in the PolicyLayer policy for performance_snapshot. 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_snapshot? +

performance_snapshot 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.

KEEP EXPLORING

More on Claude Mobile, and thousands of servers like it.

This server

All 198 Claude Mobile tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →