performance_heap_diff

Compare bounded metadata from two compatible heap artifacts. Returns signed size/count deltas; it does not claim that growth is a memory leak.

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-heap-diff.md

WHAT IT DOES

What performance_heap_diff does on Claude Mobile

AI agents call performance_heap_diff 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_heap_diff is rated Low

Reads and compares heap metadata; no side effects or data modification.

From the tool's definition Compare bounded metadata from two compatible heap artifacts

Attacks that exploit this kind of access

RECOMMENDED RULE

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

performance_heap_diff Allowed

performance_heap_diff 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_heap_diff": {}
  }
}

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_heap_diff call is checked against it from then on.

FAQ

Questions about performance_heap_diff

What does the performance_heap_diff tool do? +

Compare bounded metadata from two compatible heap artifacts. Returns signed size/count deltas; it does not claim that growth is a memory leak. 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_heap_diff? +

Register the Claude Mobile MCP server in PolicyLayer and add a rule for performance_heap_diff: 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_heap_diff? +

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

Can I rate-limit performance_heap_diff? +

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

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

performance_heap_diff 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 214 Claude Mobile tools →

Across the catalogue

binary_diff on 010 Editor → The MCP Attack Database →

Guides

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