appstore__buildler
TestFlight build'lerini listeler; işlenme durumunu ve son kullanma tarihini gösterir. En yeni build en üstte gelir. 'Yüklediğim build hazır mı' sorusunun cevabı.
This record as markdown: /tools/magaza-mcp/appstore--buildler.md
What appstore__buildler does on Magaza
AI agents invoke appstore__buildler to trigger actions in Magaza. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Kaç build dönsün (varsayılan 20). |
uygulama_id | string | — | Belirtilirse sadece o uygulamanın build'leri. |
Parameters from the server's own tool schema.
Why appstore__buildler is rated High
appstore__buildler triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs appstore__buildler safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Magaza, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For appstore__buildler, this is the rule to start with:
appstore__buildler stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Magaza, apply this rule, and every appstore__buildler call is checked against it from then on.
Questions about appstore__buildler
TestFlight build'lerini listeler; işlenme durumunu ve son kullanma tarihini gösterir. En yeni build en üstte gelir. 'Yüklediğim build hazır mı' sorusunun cevabı. It is categorised as a Execute tool in the Magaza MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
appstore__buildler accepts 2 parameters: limit, uygulama_id. The full parameter table on this page comes from the server's own tool schema.
Register the Magaza MCP server in PolicyLayer and add a rule for appstore__buildler: 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 Magaza. Nothing to install.
appstore__buildler is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the appstore__buildler 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 appstore__buildler. 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.
appstore__buildler is provided by the Magaza MCP server (magaza-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Magaza, and thousands of servers like it.
Across the catalogue