asc_post_device

SERVERAppstoreconnect Mcp SOURCE@akoskomuves/appstoreconnect-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-post-device.md

WHAT IT DOES

What asc_post_device does on Appstoreconnect Mcp

AI agents use asc_post_device to create or update resources in Appstoreconnect Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Appstoreconnect Mcp environment.

RISK

Why asc_post_device is rated Medium

Creates permanent device registration with quota consequences; reversible only via disabling, not deletion, creating resource exhaustion risk.

From the tool's definition Register a test device by UDID; registration effectively permanent; count against 100-per-class limit

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs asc_post_device safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Appstoreconnect Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For asc_post_device, this is the rule to start with:

asc_post_device Rate-limited

asc_post_device 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": {
    "asc_post_device": {
      "limits": [
        {
          "counter": "asc_post_device_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about asc_post_device

What does the asc_post_device tool do? +

Register a test device by UDID. ⚠️ Registration is effectively permanent: devices can never be deleted (only DISABLED) and count against the 100-per-class membership-year limit until Apple’s yearly reset — check the UDID carefully. It is categorised as a Write tool in the Appstoreconnect Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on asc_post_device? +

Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_post_device: 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 Appstoreconnect Mcp. Nothing to install.

What risk level is asc_post_device? +

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

Can I rate-limit asc_post_device? +

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

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

asc_post_device is provided by the Appstoreconnect MCP server (@akoskomuves/appstoreconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Appstoreconnect, and thousands of servers like it.

This server

All 363 Appstoreconnect tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →