run_workflow
Run an existing Sanka-native workflow definition. HubSpot workflow creation and updates use create_workflow/update_workflow with provider=hubspot.
This record as markdown: /tools/sankahq-sanka-mcp/run-workflow.md
What run_workflow does on Sanka MCP Server
AI agents invoke run_workflow to trigger actions in Sanka 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.
Why run_workflow is rated High
The tool executes a predefined workflow, which is an operational action that triggers automation logic external to the MCP server itself. While the specific side effects depend on what the workflow contains, execution tools that trigger business processes (especially when considering sibling tools like activate_invoice, activate_order, approve_payroll_run) pose significant risk if invoked with incorrect parameters…
From the tool's definition Tool performs 'Run an existing Sanka-native workflow definition' — a workflow execution that triggers external operations whose effects depend on the workflow's configured logic and arguments.
Attacks that exploit this kind of access
The rule that runs run_workflow safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_workflow, this is the rule to start with:
run_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 Sanka MCP Server, apply this rule, and every run_workflow call is checked against it from then on.
Questions about run_workflow
Run an existing Sanka-native workflow definition. HubSpot workflow creation and updates use create_workflow/update_workflow with provider=hubspot. It is categorised as a Execute tool in the Sanka MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for run_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 Sanka MCP Server. Nothing to install.
run_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 run_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 run_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.
run_workflow is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sanka MCP Server, and thousands of servers like it.
Across the catalogue