Critical Risk →

workflows.get

Get detailed workflow information (note: create/update/delete operations not supported for safety).

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

app-store-connect-mcp Destructive Risk 4/5

AI agents may call workflows.get to permanently remove or destroy resources in App Store Connect. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call workflows.get in a loop, permanently destroying resources in App Store Connect. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

io-github-gjeltep-app-store-connect-mcp.yaml
tools:
  workflows.get:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full App Store Connect policy for all 31 tools.

Tool Name workflows.get
Category Destructive
Risk Level Critical

View all 31 tools →

Agents calling destructive-class tools like workflows.get 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 Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

workflows.get is one of the critical-risk operations in App Store Connect. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the workflows.get tool do? +

Get detailed workflow information (note: create/update/delete operations not supported for safety).. It is categorised as a Destructive tool in the App Store Connect MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on workflows.get? +

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

What risk level is workflows.get? +

workflows.get is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit workflows.get? +

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

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

workflows.get is provided by the App Store Connect MCP server (app-store-connect-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on App Store Connect

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.