Low Risk

crashes.get_log

Retrieve the raw crash log text for a specific submission.

Single-target operation

Part of the App Store Connect MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call crashes.get_log to retrieve information from App Store Connect without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though crashes.get_log only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-gjeltep-app-store-connect-mcp.yaml
tools:
  crashes.get_log:
    rules:
      - action: allow

See the full App Store Connect policy for all 31 tools.

Tool Name crashes.get_log
Category Read
Risk Level Low

View all 31 tools →

Agents calling read-class tools like crashes.get_log have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the crashes.get_log tool do? +

Retrieve the raw crash log text for a specific submission.. It is categorised as a Read tool in the App Store Connect MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on crashes.get_log? +

Add a rule in your Intercept YAML policy under the tools section for crashes.get_log. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the App Store Connect MCP server.

What risk level is crashes.get_log? +

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

Can I rate-limit crashes.get_log? +

Yes. Add a rate_limit block to the crashes.get_log rule in your Intercept 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 crashes.get_log completely? +

Set action: deny in the Intercept policy for crashes.get_log. 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 crashes.get_log? +

crashes.get_log is provided by the App Store Connect MCP server (app-store-connect-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on App Store Connect

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.