API-v1_0_upload-file_create · Magicpod MCP: Risk & Policy

WHAT IT DOES

What API-v1_0_upload-file_create does on Magicpod

AI agents use API-v1_0_upload-file_create to create or update resources in Magicpod — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Magicpod environment.

WHY IT NEEDS A POLICY

Why API-v1_0_upload-file_create needs a policy

Uploading files to a cloud service is a write operation that creates or stores data. The severity is high because uploading malicious or incorrect app binaries could compromise testing infrastructure, inject malware into CI/CD pipelines, or enable unauthorized deployment of compromised applications.

From the tool's definition Tool description states 'Upload target app files (.ipa, .apk, .aab, or zipped .app) to MagicPod cloud' - the verb 'upload' indicates creation/storage of new data in a cloud system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

API-v1_0_upload-file_create Rate-limited

API-v1_0_upload-file_create stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "API-v1_0_upload-file_create": {
      "limits": [
        {
          "counter": "api-v1_0_upload-file_create_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Magicpod, so you can run agents against it safely.

FAQ

Questions about API-v1_0_upload-file_create

What does the API-v1_0_upload-file_create tool do? +

Upload target app files (.ipa, .apk, .aab, or zipped .app) to MagicPod cloud. It is categorised as a Write tool in the Magicpod MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on API-v1_0_upload-file_create? +

Register the Magicpod MCP server in PolicyLayer and add a rule for API-v1_0_upload-file_create: 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 Magicpod. Nothing to install.

What risk level is API-v1_0_upload-file_create? +

API-v1_0_upload-file_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit API-v1_0_upload-file_create? +

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

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

API-v1_0_upload-file_create is provided by the Magicpod MCP server (magic-pod/magicpod-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.