play__uygulamalar

Servis hesabının eriştiği Google Play uygulamalarını listeler. Diğer play__ araçlarının istediği paket adını (packageName) buradan al. Not: bu liste Play Developer Reporting API'sinden gelir, çünkü Android Publisher API'sinde uygulama listeleme uç noktası yoktur.

SERVERMagaza SOURCEmagaza-mcp

Low RISK CLASS

Category Other

Parameters 10 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/magaza-mcp/play--uygulamalar.md

WHAT IT DOES

What play__uygulamalar does on Magaza

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

Parameter	Type	Required	Description
`limit`	number	—	Kaç uygulama dönsün (varsayılan 50, en çok 1000).

Parameters from the server's own tool schema.

RISK

Why play__uygulamalar is rated Low

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

Attacks that exploit this kind of access

RECOMMENDED RULE

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

play__uygulamalar Rate-limited

play__uygulamalar gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "play__uygulamalar": {
      "limits": [
        {
          "counter": "play__uygulamalar_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about play__uygulamalar

What does the play__uygulamalar tool do? +

What parameters does play__uygulamalar accept? +

play__uygulamalar accepts 1 parameter: limit. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on play__uygulamalar? +

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

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

Can I rate-limit play__uygulamalar? +

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

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

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

KEEP EXPLORING

More on Magaza, and thousands of servers like it.

This server

All 39 Magaza tools →

Across the catalogue

play_music on Redmine Analytics and Automation MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →