unlink_app_workflow

Unlink a workflow from an app. After unlinking, the app will no longer be able to invoke that workflow. Make sure to update your app code to remove any references to the unlinked workflow.

SERVERFlowDot MCP Server SOURCEflowdot-llc/mcp-server

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/flowdot-llc-mcp-server/unlink-app-workflow.md

WHAT IT DOES

What unlink_app_workflow does on FlowDot MCP Server

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

RISK

Why unlink_app_workflow is rated Medium

This tool removes an association between an app and a workflow, which is a reversible configuration change (the workflow can presumably be re-linked). It modifies a relationship/binding rather than deleting data permanently, placing it in the Write category. The severity is medium because unlinking could break app functionality if references aren't removed, but the action itself is not irreversible.

From the tool's definition Unlink a workflow from an app. After unlinking, the app will no longer be able to invoke that workflow.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs unlink_app_workflow safely

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

unlink_app_workflow Rate-limited

unlink_app_workflow 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": {
    "unlink_app_workflow": {
      "limits": [
        {
          "counter": "unlink_app_workflow_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 FlowDot MCP Server, apply this rule, and every unlink_app_workflow call is checked against it from then on.

FAQ

Questions about unlink_app_workflow

What does the unlink_app_workflow tool do? +

Unlink a workflow from an app. After unlinking, the app will no longer be able to invoke that workflow. Make sure to update your app code to remove any references to the unlinked workflow. It is categorised as a Write tool in the FlowDot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on unlink_app_workflow? +

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

What risk level is unlink_app_workflow? +

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

Can I rate-limit unlink_app_workflow? +

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

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

unlink_app_workflow is provided by the FlowDot MCP Server MCP server (flowdot-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on FlowDot MCP Server, and thousands of servers like it.

This server

All 207 FlowDot MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

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