update_workflow · Sanka MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_workflow does on Sanka MCP Server

AI agents use update_workflow to create or update resources in Sanka MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sanka MCP Server environment.

WHY IT NEEDS A POLICY

Why update_workflow needs a policy

The tool modifies workflow definitions in Sanka or external providers (HubSpot), which affects business process automation. While updates are theoretically reversible (unlike deletion), incorrect workflow modifications could disrupt critical business processes, trigger unintended automations, or affect downstream operations.

From the tool's definition Tool performs 'Update' operation on workflow definitions, explicitly stated as 'Update a Sanka workflow definition or a provider workflow'. Updates are reversible modifications that change system state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_workflow Rate-limited

update_workflow stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_workflow": {
      "limits": [
        {
          "counter": "update_workflow_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Sanka MCP Server, so you can run agents against it safely.

FAQ

Questions about update_workflow

What does the update_workflow tool do? +

Update a Sanka workflow definition or a provider workflow by passing provider=hubspot through the same workflow endpoint. HubSpot updates require workflow_id or external_id as the HubSpot flow id. It is categorised as a Write tool in the Sanka MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_workflow? +

Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_workflow? +

update_workflow is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_workflow? +

Yes. Add a rate_limit block to the update_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.

How do I block update_workflow completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_workflow? +

update_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.