re-ios

dynamic_hook_iap

Intercept In-App Purchase transactions in a running iOS app by hooking StoreKit methods to log purchases, product requests, and receipt validation.

Instructions

Inject IAP (In-App Purchase) hook into a running iOS app.

Hooks StoreKit/SKPaymentQueue methods to log purchase transactions, product requests, and receipt validation attempts.

Args: target: Bundle ID or PID of the target app device_type: Device type: 'usb', 'local', or 'remote' (default: 'usb') device_id: Specific device ID (optional) duration: Monitoring duration in seconds (default: 30)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "target": "<target>"
    },
    "name": "dynamic_hook_iap"
  }
}

Input Schema

Name	Required	Default
`target`	Yes
`duration`	No
`device_id`	No
`device_type`	No	usb

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Jul 9, 2026

TDQS

A3.7/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden. It explains what methods are hooked and what is logged, but lacks disclosure of potential side effects (e.g., app crashes, detection risks, performance impact) or whether the hook is reversible. Does not state if results are printed to console or saved.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (3 sentences plus an Args block) and front-loaded. Every sentence serves a purpose: what it does, what it hooks, and parameter details. No redundancy or wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and moderate complexity (hooking a running app), the description lacks explanation of return values or output format (e.g., logs, console output, file). It does not mention cleanup after duration or how to verify hook success. Missing context for a tool that modifies runtime behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so description must compensate. It explains all 4 parameters: target (bundle ID or PID), device_type (usb/local/remote), device_id (optional specific device), and duration (monitoring seconds). This adds meaningful context beyond the schema's type-only definitions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Inject IAP hook into a running iOS app' with specific verbs and resources, and explicitly lists hooked StoreKit methods (SKPaymentQueue, purchase transactions, product requests, receipt validation). This distinguishes it from sibling hook tools like dynamic_hook_network.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives (e.g., dynamic_hook_network or other analysis tools). The description does not mention prerequisites, scenarios, or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.