create_provisioning_workflow
AI agents invoke create_provisioning_workflow to trigger actions in Morpheus 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.
The tool name strongly implies creating and triggering provisioning workflows, which involves executing infrastructure operations. Given the server context of cloud infrastructure management, creating a provisioning workflow would initiate external operations (spinning up instances, configuring resources, etc.). Severity is high due to the potential blast radius of unintended infrastructure provisioning.
From the tool's definition Tool name 'create_provisioning_workflow' on a server that 'enables users to provision resources, execute workflows'; description is empty and uninformative.
Attacks that exploit this kind of access
create_provisioning_workflow. It is categorised as a Execute tool in the Morpheus MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Morpheus MCP Server MCP server in PolicyLayer and add a rule for create_provisioning_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 Morpheus MCP Server. Nothing to install.
create_provisioning_workflow 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 create_provisioning_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.
Set action: deny in the PolicyLayer policy for create_provisioning_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.
create_provisioning_workflow is provided by the Morpheus MCP Server MCP server (nixndme/morpheus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
create_provisioning_workflow is one line of Morpheus MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →