Low Risk

report_instances.list_segments

List data segments for a report instance.

Part of the App Store Connect server.

report_instances.list_segments is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE APP STORE CONNECT →

Free to start. No card required.

AI agents call report_instances.list_segments 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 report_instances.list_segments 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "report_instances.list_segments": {}
  }
}

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

Get this rule live on your own App Store Connect server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY APP STORE CONNECT →

View all 31 tools →

These attack patterns abuse exactly the kind of access report_instances.list_segments gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so report_instances.list_segments only ever does what you allow.

SECURE APP STORE CONNECT →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the report_instances.list_segments tool do? +

List data segments for a report instance.. 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 report_instances.list_segments? +

Register the App Store Connect MCP server in PolicyLayer and add a rule for report_instances.list_segments: 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 App Store Connect. Nothing to install.

What risk level is report_instances.list_segments? +

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

Can I rate-limit report_instances.list_segments? +

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

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

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

Enforce policy on every App Store Connect tool call.

Deterministic rules across all 31 App Store Connect tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.