Execution Authorization-gate component for Dify workflows exposed as MCP servers (uses aiyoplane-mcp-authz)

[rashonmassey]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Hello!

So there’s work that's happening (like in #39240) showing that Dify workflows can be exposed as MCP servers, turning every workflow into a tool that an MCP client can call autonomously ....which is awesome, but when one of those workflow nodes performs a data write, deploy, payment, outbound API or any Consequential Action, the per-invocation authorization decision isn’t addressed inside the workflow itself.

That being said, my team over at Aiyoplane shipped a Python middleware, aiyoplane-mcp-authz (source, Apache 2.0, zero credentials to run locally), that attaches a Runtime Decision Point above the tool-invocation point. ALLOW / ESCALATE / BLOCK, with a cryptographically-signed Execution Receipt attached to flow context on ALLOW. The spec is at github.com/aiyoplane/aeap.

Rough shape of what a Dify execution authorization-gate wrapping it would look like, and we intentionally kept it thin:

from aiyoplane_mcp_authz import create_aiyo_mcp_authz, create_local_rdp, BlockedByPolicy

authz = create_aiyo_mcp_authz(
    rdp=create_local_rdp(policy=load_policy("policy.yaml")),
    tool_config={
        "send_payment": {"aiyo_gated": True, "action": {"type": "payment"}},
    },
)

@authz.wrap("send_payment")
def send_payment(args, ctx):
    # Runs only on ALLOW. ctx.receipt is the verified Execution Receipt.
    return perform_payment(args)
# ESCALATE / BLOCK raise typed exceptions the Dify node can catch.

So now we just have a question for the maintainers: what distribution shape would fit Dify best? A plugin in the Dify Marketplace (like #39210), a custom tool, or a workflow-node extension?

AEAP is an open protocol, so we're happy to build to whichever shape makes sense!

Repo: github.com/aiyoplane/mcp-authz-python · Spec: github.com/aiyoplane/aeap · Trust: aiyoplane.com/trust

Thanks a lot!

2. Additional context or comments

No response

3. Can you help us with this feature?

• I am interested in contributing to this feature.