Medium Risk

create_app_version

Create a new App Store version for an app.

Part of the Asc server.

create_app_version can modify Asc data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE ASC →

Free to start. No card required.

AI agents use create_app_version to create or modify resources in Asc. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call create_app_version repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Asc.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_app_version": {
      "limits": [
        {
          "counter": "create_app_version_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Asc policy for all 38 tools.

Get this rule live on your own Asc server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY ASC →

View all 38 tools →

These attack patterns abuse exactly the kind of access create_app_version gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so create_app_version only ever does what you allow.

SECURE ASC →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the create_app_version tool do? +

Create a new App Store version for an app.. It is categorised as a Write tool in the Asc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_app_version? +

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

What risk level is create_app_version? +

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

Can I rate-limit create_app_version? +

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

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

create_app_version is provided by the Asc MCP server (asc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Asc tool call.

Deterministic rules across all 38 Asc tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.