asc_get_app_perf_power_metrics
GET /v1/apps/{id}/perfPowerMetrics — Xcode-metrics percentile curves (LAUNCH, MEMORY, BATTERY, HANG, DISK, ANIMATION, TERMINATION, STORAGE) per device class, rolling across recent versions. NOT JSON:API: content type application/vnd.apple.xcode-metrics+json, returned as raw JSON (capped at maxCha...
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-get-app-perf-power-metrics.md
What asc_get_app_perf_power_metrics does on Appstoreconnect Mcp
AI agents call asc_get_app_perf_power_metrics to retrieve information from Appstoreconnect Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why asc_get_app_perf_power_metrics is rated Low
This tool performs a read-only operation that queries and retrieves application performance metrics from App Store Connect. The GET HTTP verb and the absence of any data modification, deletion, or execution capabilities confirm it is a simple data retrieval operation. The severity is low because metrics data is informational with minimal blast radius if accessed by an AI agent without proper authorization.
From the tool's definition GET /v1/apps/{id}/perfPowerMetrics — retrieves performance metrics (LAUNCH, MEMORY, BATTERY, HANG, DISK, ANIMATION, TERMINATION, STORAGE) per device class; query parameters (metricType/deviceType) allow filtering; response is raw JSON metrics data with no…
Attacks that exploit this kind of access
The rule that runs asc_get_app_perf_power_metrics safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appstoreconnect Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For asc_get_app_perf_power_metrics, this is the rule to start with:
asc_get_app_perf_power_metrics is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Appstoreconnect Mcp, apply this rule, and every asc_get_app_perf_power_metrics call is checked against it from then on.
Questions about asc_get_app_perf_power_metrics
GET /v1/apps/{id}/perfPowerMetrics — Xcode-metrics percentile curves (LAUNCH, MEMORY, BATTERY, HANG, DISK, ANIMATION, TERMINATION, STORAGE) per device class, rolling across recent versions. NOT JSON:API: content type application/vnd.apple.xcode-metrics+json, returned as raw JSON (capped at maxChars). Narrow with metricType/deviceType (e.g. deviceType. It is categorised as a Read tool in the Appstoreconnect Mcp MCP Server, which means it retrieves data without modifying state.
Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_get_app_perf_power_metrics: 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 Appstoreconnect Mcp. Nothing to install.
asc_get_app_perf_power_metrics is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the asc_get_app_perf_power_metrics 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 asc_get_app_perf_power_metrics. 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.
asc_get_app_perf_power_metrics is provided by the Appstoreconnect MCP server (@akoskomuves/appstoreconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appstoreconnect, and thousands of servers like it.
This server
Across the catalogue