unlink_app_toolkit
Unlink a toolkit from an app. After unlinking, the app will no longer be able to invoke that toolkit
This record as markdown: /tools/flowdot-llc-mcp-server/unlink-app-toolkit.md
What unlink_app_toolkit does on FlowDot MCP Server
AI agents invoke unlink_app_toolkit to trigger actions in FlowDot MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why unlink_app_toolkit is rated High
unlink_app_toolkit triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs unlink_app_toolkit 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_toolkit, this is the rule to start with:
unlink_app_toolkit stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FlowDot MCP Server, apply this rule, and every unlink_app_toolkit call is checked against it from then on.
Questions about unlink_app_toolkit
Unlink a toolkit from an app. After unlinking, the app will no longer be able to invoke that toolkit. It is categorised as a Execute tool in the FlowDot MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for unlink_app_toolkit: 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.
unlink_app_toolkit is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the unlink_app_toolkit 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.
Set action: deny in the PolicyLayer policy for unlink_app_toolkit. 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.
unlink_app_toolkit 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.
More on FlowDot MCP Server, and thousands of servers like it.
Across the catalogue