magaza__cagir
App Store Connect ve Google Play API'lerinde herhangi bir operasyonu çalıştırır. Operasyon adını önce magaza__endpoint_ara ile bul. Veri değiştiren işlemler (POST/PATCH/PUT/DELETE) onayla=true verilmeden çalışmaz.
This record as markdown: /tools/magaza-mcp/magaza--cagir.md
What magaza__cagir does on Magaza
AI agents call magaza__cagir to permanently remove resources in Magaza, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
govde | object | — | İstek gövdesi (POST/PATCH için). |
magaza | string | Yes | Hangi mağaza. |
onayla | boolean | — | Veri değiştiren işlemler için true olmalı. Kullanıcı işlemi açıkça istemeden true verme. |
operasyon | string | Yes | magaza__endpoint_ara sonucundaki 'operasyon' değeri. |
parametreler | object | — | Yol ve sorgu parametreleri tek bir nesnede. Yol parametreleri otomatik yerine konur, kalanlar sorgu dizesine eklenir. |
Parameters from the server's own tool schema.
Why magaza__cagir is rated Critical
An AI agent that decides to call magaza__cagir doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Magaza is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs magaza__cagir 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 magaza__cagir, this is the rule to start with:
magaza__cagir is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Magaza, apply this rule, and every magaza__cagir call is checked against it from then on.
Questions about magaza__cagir
App Store Connect ve Google Play API'lerinde herhangi bir operasyonu çalıştırır. Operasyon adını önce magaza__endpoint_ara ile bul. Veri değiştiren işlemler (POST/PATCH/PUT/DELETE) onayla=true verilmeden çalışmaz. It is categorised as a Destructive tool in the Magaza MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
magaza__cagir accepts 5 parameters: govde, magaza, onayla, operasyon, parametreler. Required: magaza, operasyon. 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 magaza__cagir: 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.
magaza__cagir is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the magaza__cagir 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 magaza__cagir. 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.
magaza__cagir 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