Rename a folder or update its description
AI agents use signavio_update_folder to create or update resources in Signavio MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Signavio MCP Server environment.
This tool creates or modifies data (folder name/description) without permanently destroying it. Changes can be undone by renaming/updating again. It does not delete, execute code, move money, or read/search. Medium severity reflects that corrupting folder metadata in a business process management system could disrupt organization and navigation of critical process models, but the changes are reversible.
From the tool's definition Tool description states 'Rename a folder or update its description' — these are reversible modifications to folder metadata.
Documented attack patterns abuse exactly the kind of access signavio_update_folder gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Signavio MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for signavio_update_folder:
{
"version": "1",
"default": "deny",
"tools": {
"signavio_update_folder": {
"limits": [
{
"counter": "signavio_update_folder_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} signavio_update_folder 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.
Rename a folder or update its description. It is categorised as a Write tool in the Signavio MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Signavio MCP Server MCP server in PolicyLayer and add a rule for signavio_update_folder: 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 Signavio MCP Server. Nothing to install.
signavio_update_folder 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 signavio_update_folder 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 signavio_update_folder. 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.
signavio_update_folder is provided by the Signavio MCP Server MCP server (willpowell8/signavio-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Signavio MCP Server, 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.
23 Signavio MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.