Move a folder to a new parent or to trash
AI agents use signavio_move_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 modifies data structure and organizational hierarchy by relocating folders, making it a Write operation rather than Destructive. While moving to trash is a step toward deletion, it is typically reversible in modern systems. If the tool permanently deleted without recovery option, it would be Destructive.
From the tool's definition Tool description states "Move a folder to a new parent or to trash", which modifies the location/structure of data.
Documented attack patterns abuse exactly the kind of access signavio_move_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_move_folder:
{
"version": "1",
"default": "deny",
"tools": {
"signavio_move_folder": {
"limits": [
{
"counter": "signavio_move_folder_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} signavio_move_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.
Move a folder to a new parent or to trash. 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_move_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_move_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_move_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_move_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_move_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.