crm_run_ai_workflow
Execute an AI Workflow (Agent Studio agent). Send a message and get a response. Maintains conversation context via executionId.
This record as markdown: /tools/io-github-0nork-0nmcp/crm-run-ai-workflow.md
What crm_run_ai_workflow does on 0nmcp
AI agents invoke crm_run_ai_workflow to trigger actions in 0nmcp. 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 crm_run_ai_workflow is rated High
This tool executes arbitrary AI workflows/agents with effects determined by the user-supplied message and the target workflow. While it doesn't directly delete data or move money, it can trigger side effects through whatever logic the workflow implements. The high severity reflects that a compromised or malicious workflow could perform destructive, financial, or other harmful operations.
From the tool's definition 'Execute an AI Workflow (Agent Studio agent)' and 'Send a message and get a response' with 'maintains conversation context' indicates running external code/agents whose effects depend on the workflow content and input arguments.
Attacks that exploit this kind of access
The rule that runs crm_run_ai_workflow safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0nmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crm_run_ai_workflow, this is the rule to start with:
crm_run_ai_workflow 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 0nmcp, apply this rule, and every crm_run_ai_workflow call is checked against it from then on.
Questions about crm_run_ai_workflow
Execute an AI Workflow (Agent Studio agent). Send a message and get a response. Maintains conversation context via executionId. It is categorised as a Execute tool in the 0nmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the 0n MCP server in PolicyLayer and add a rule for crm_run_ai_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 0nmcp. Nothing to install.
crm_run_ai_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 crm_run_ai_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 crm_run_ai_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.
crm_run_ai_workflow is provided by the 0n MCP server (0nmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0n, and thousands of servers like it.
This server
Across the catalogue