New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

appstore__iap_fiyat_ayarla

Tek seferlik uygulama içi satın almanın fiyatını ayarlar. Bir ülkedeki fiyatı verirsin, Apple diğer bütün ülkeleri kendisi doldurur (tek istek). Mevcut fiyat takviminin yerine geçer.

SERVERMagaza SOURCEmagaza-mcp
Low RISK CLASS
Category Other
Parameters 52 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/magaza-mcp/appstore--iap-fiyat-ayarla.md

What appstore__iap_fiyat_ayarla does on Magaza

AI agents call appstore__iap_fiyat_ayarla as a supporting operation in Magaza workflows.

ParameterTypeRequiredDescription
ulke string — Fiyatın verildiği ülke (3 harf). Varsayılan USA; diğer ülkeler buna eşitlenir.
fiyat string Yes Müşterinin ödeyeceği fiyat, o ülkenin para biriminde (örn. "9.99").
iap_id string Yes appstore__iap_urunler'den gelen ürün id'si.
onayla boolean — Veri değiştiren işlemler için true olmalı. Kullanıcı işlemi açıkça istemeden true verme.
baslangic string — Yeni fiyatın başlayacağı gün (YYYY-AA-GG). Boşsa hemen.

Parameters from the server's own tool schema.

Why appstore__iap_fiyat_ayarla is rated Low

Without any rule in front of it, every call an agent makes to appstore__iap_fiyat_ayarla happens silently: no trail, no cap, no way to know it misbehaved until something breaks downstream.

Questions about appstore__iap_fiyat_ayarla

What does the appstore__iap_fiyat_ayarla tool do? +

Tek seferlik uygulama içi satın almanın fiyatını ayarlar. Bir ülkedeki fiyatı verirsin, Apple diğer bütün ülkeleri kendisi doldurur (tek istek). Mevcut fiyat takviminin yerine geçer. It is categorised as a Other tool in the Magaza MCP Server, which means it performs auxiliary operations.

What parameters does appstore__iap_fiyat_ayarla accept? +

appstore__iap_fiyat_ayarla accepts 5 parameters: ulke, fiyat, iap_id, onayla, baslangic. Required: fiyat, iap_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on appstore__iap_fiyat_ayarla? +

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

What risk level is appstore__iap_fiyat_ayarla? +

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

Can I rate-limit appstore__iap_fiyat_ayarla? +

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

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

appstore__iap_fiyat_ayarla 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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Magaza's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.