rename_workflow_execution

Give a custom name to your workflow execution session for easier identification.

SERVERAutomagik Tools SOURCEnamastexlabs/automagik-tools

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/namastexlabs-automagik-tools/rename-workflow-execution.md

WHAT IT DOES

What rename_workflow_execution does on Automagik Tools

AI agents use rename_workflow_execution to create or update resources in Automagik Tools, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Automagik Tools environment.

RISK

Why rename_workflow_execution is rated Medium

The tool updates workflow execution session names, which is reversible metadata modification. It does not delete data (not Destructive), execute arbitrary code (not Execute), move money (not Financial), or read-only retrieve data (not Read). The blast radius is minimal—renaming sessions affects only identification/organization without impacting data integrity or system behavior.

From the tool's definition Tool performs 'Give a custom name' operation which modifies metadata of a workflow execution session. This is a write operation that creates or updates naming information.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs rename_workflow_execution safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Automagik Tools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rename_workflow_execution, this is the rule to start with:

rename_workflow_execution Rate-limited

rename_workflow_execution 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": {
    "rename_workflow_execution": {
      "limits": [
        {
          "counter": "rename_workflow_execution_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Automagik Tools, apply this rule, and every rename_workflow_execution call is checked against it from then on.

FAQ

Questions about rename_workflow_execution

What does the rename_workflow_execution tool do? +

Give a custom name to your workflow execution session for easier identification. It is categorised as a Write tool in the Automagik Tools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rename_workflow_execution? +

Register the Automagik Tools MCP server in PolicyLayer and add a rule for rename_workflow_execution: 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 Automagik Tools. Nothing to install.

What risk level is rename_workflow_execution? +

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

Can I rate-limit rename_workflow_execution? +

Yes. Add a rate_limit block to the rename_workflow_execution 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 rename_workflow_execution completely? +

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

rename_workflow_execution is provided by the Automagik Tools MCP server (namastexlabs/automagik-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Automagik Tools, and thousands of servers like it.

This server

All 122 Automagik Tools tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →