Give a custom name to your workflow execution session for easier identification.
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.
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.
Documented attack patterns abuse exactly the kind of access rename_workflow_execution gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Automagik Tools, and nothing reaches the server without passing your rules. This is the rule we recommend for rename_workflow_execution:
{
"version": "1",
"default": "deny",
"tools": {
"rename_workflow_execution": {
"limits": [
{
"counter": "rename_workflow_execution_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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.
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.
rename_workflow_execution is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
Start from Automagik Tools, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
122 Automagik Tools tools catalogued and risk-classified — across an index of 43,000+ MCP servers.