Medium Risk

appstore_push_metadata

Push translated metadata to App Store Connect. Requires version_id from appstore_fetch_metadata. Updates name, subtitle, description, keywords, and/or what's new for specified locales.

Handles credentials or secrets (private_key); High parameter count (12 properties)

Part of the Locaflow MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use appstore_push_metadata to create or modify resources in Locaflow. 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 appstore_push_metadata repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Locaflow.

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

locaflow.yaml
tools:
  appstore_push_metadata:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Locaflow policy for all 6 tools.

Tool Name appstore_push_metadata
Category Write
MCP Server Locaflow MCP Server
Risk Level Medium

Agents calling write-class tools like appstore_push_metadata have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the appstore_push_metadata tool do? +

Push translated metadata to App Store Connect. Requires version_id from appstore_fetch_metadata. Updates name, subtitle, description, keywords, and/or what's new for specified locales.. It is categorised as a Write tool in the Locaflow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on appstore_push_metadata? +

Add a rule in your Intercept YAML policy under the tools section for appstore_push_metadata. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Locaflow MCP server.

What risk level is appstore_push_metadata? +

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

Can I rate-limit appstore_push_metadata? +

Yes. Add a rate_limit block to the appstore_push_metadata rule in your Intercept 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_push_metadata completely? +

Set action: deny in the Intercept policy for appstore_push_metadata. 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_push_metadata? +

appstore_push_metadata is provided by the Locaflow MCP server (locaflow-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.