workflow.generate_original_asset
Launch an explicitly L0 generated-design portfolio without measured-target claims.
This record as markdown: /tools/visionmcp/workflow.generate-original-asset.md
What workflow.generate_original_asset does on Visionmcp
AI agents invoke workflow.generate_original_asset to trigger actions in Visionmcp. 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 workflow.generate_original_asset is rated High
The tool launches/initiates a generation process (producing a design portfolio asset), which constitutes executing an external operation. It doesn't merely read data, nor does it clearly modify existing records (Write), delete anything (Destructive), or involve money (Financial). The 'Launch' terminology combined with asset generation places it in Execute.
From the tool's definition 'Launch an explicitly L0 generated-design portfolio' — the word 'Launch' indicates triggering an external operation or generation process
Attacks that exploit this kind of access
The rule that runs workflow.generate_original_asset safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Visionmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For workflow.generate_original_asset, this is the rule to start with:
workflow.generate_original_asset 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 Visionmcp, apply this rule, and every workflow.generate_original_asset call is checked against it from then on.
Questions about workflow.generate_original_asset
Launch an explicitly L0 generated-design portfolio without measured-target claims. It is categorised as a Execute tool in the Visionmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Vision MCP server in PolicyLayer and add a rule for workflow.generate_original_asset: 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 Visionmcp. Nothing to install.
workflow.generate_original_asset 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 workflow.generate_original_asset 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 workflow.generate_original_asset. 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.
workflow.generate_original_asset is provided by the Vision MCP server (joshuahickscorp/visionmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vision, and thousands of servers like it.
Across the catalogue