qflow_plugin

THE RISK

High Risk

Why qflow_plugin needs a policy

This tool manages plugins including installing and removing them. Installing plugins executes external code/packages on the system, and removing them is potentially destructive.

From the tool's definition install=安装插件，remove=卸载，list=列表，get=详情，search=搜索，enable=启用，disable=禁用 (plugin management: install, remove, list, get details, search, enable, disable)

Documented attack patterns abuse exactly the kind of access qflow_plugin gives an agent:

POLICY

How to control qflow_plugin

PolicyLayer is an MCP gateway — it sits between your AI agents and Qflow, and nothing reaches the server without passing your rules. This is the rule we recommend for qflow_plugin:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "qflow_plugin": {
      "limits": [
        {
          "counter": "qflow_plugin_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

qflow_plugin 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.

Create a free account and register Qflow — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Qflow tools

Destructive qflow_task_delete 删除任务。cascade=true 时同时删除子任务，并清理其他任务中的依赖引用。 Execute qflow_tdd 合并 TDD 工具。action: preset(查询预设)/step(单步执行)/loop(完整循环)/status(状态)/reset(重置)。 Execute qflow_autopilot 合并自动驾驶工具。action: config(配置)/start(启动)/pause(暂停)/resume(恢复)/status(状态)/stop(停止)/step(单步)/co Execute qflow_workflow DAG 工作流管理：start=启动工作流，advance=推进工作流，status=查看状态，list=列出所有工作流 Execute qflow_agile 敏捷工作流预设：list=列出所有阶段，get=获取指定阶段，step=执行步骤 Write qflow_parse_prd 解析 PRD（产品需求文档）的 Markdown 内容，自动生成结构化任务列表。标题→任务，子标题→子任务。 Write qflow_scope_navigate 作用域导航：up=子任务提升为顶层任务, down=顶层任务降级为子任务, adjust=动态调节任务范围 Write qflow_constitution 合并治理原则工具。action: init(初始化)/get(获取列表)/set(添加原则)/validate(验证内容)。

All 50 Qflow tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Qflow → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about qflow_plugin

What does the qflow_plugin tool do? +

插件管理：install=安装插件，remove=卸载，list=列表，get=详情，search=搜索，enable=启用，disable=禁用. It is categorised as a Execute tool in the Qflow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on qflow_plugin? +

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

What risk level is qflow_plugin? +

qflow_plugin is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit qflow_plugin? +

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

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

qflow_plugin is provided by the Qflow MCP server (pangu-immortal/qflow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Qflow tool call.

Start from Qflow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →