asc_get_ci_build_run

Fetch one build run with source/destination commit details, issue counts, progress/completion status and start/cancel reasons. Raw JSON (the commit structs are nested).

SERVERAppstoreconnect Mcp SOURCE@akoskomuves/appstoreconnect-mcp

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/io-github-akoskomuves-appstoreconnect-mcp/asc-get-ci-build-run.md

WHAT IT DOES

What asc_get_ci_build_run does on Appstoreconnect Mcp

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

RISK

Why asc_get_ci_build_run is rated Low

Tool retrieves CI build run metadata without modifying or executing operations.

From the tool's definition Fetch one build run with source/destination commit details, issue counts, progress/completion status

Attacks that exploit this kind of access

RECOMMENDED RULE

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

asc_get_ci_build_run Allowed

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Appstoreconnect Mcp, apply this rule, and every asc_get_ci_build_run call is checked against it from then on.

FAQ

Questions about asc_get_ci_build_run

What does the asc_get_ci_build_run tool do? +

Fetch one build run with source/destination commit details, issue counts, progress/completion status and start/cancel reasons. Raw JSON (the commit structs are nested). It is categorised as a Read tool in the Appstoreconnect Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on asc_get_ci_build_run? +

Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_get_ci_build_run: 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.

What risk level is asc_get_ci_build_run? +

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

Can I rate-limit asc_get_ci_build_run? +

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

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

asc_get_ci_build_run 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.

KEEP EXPLORING

More on Appstoreconnect, and thousands of servers like it.

This server

All 363 Appstoreconnect tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

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