signavio_move_model

THE RISK

Medium Risk

Why signavio_move_model needs a policy

This tool changes the organizational structure and location of a process model within the folder hierarchy. While reversible (the model can be moved again), it modifies data state and could disrupt workflow organization or access patterns if misused by an AI agent. It is not Read (performs an action beyond retrieval), not Destructive (the model itself is not deleted), and not Execute/Financial/Other.

From the tool's definition 'Move a model to a different folder' - the tool modifies the location/metadata of an existing model by changing its parent folder, which is a reversible structural change to the model hierarchy.

Documented attack patterns abuse exactly the kind of access signavio_move_model gives an agent:

POLICY

How to control signavio_move_model

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_model:

policy.json

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

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

Create a free account and register Signavio MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Signavio MCP Server tools

Destructive signavio_delete_dictionary_entry Delete a dictionary entry Destructive signavio_delete_folder Permanently delete a folder and all its contents Write signavio_create_dictionary_category Create a new dictionary category Write signavio_create_dictionary_entry Create a new dictionary entry Write signavio_create_folder Create a new folder Write signavio_create_model Create a new model/diagram Write signavio_move_folder Move a folder to a new parent or to trash Write signavio_publish_model Publish one or more models to Process Collaboration Hub

All 23 Signavio MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about signavio_move_model

What does the signavio_move_model tool do? +

Move a model to a different folder. 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.

How do I enforce a policy on signavio_move_model? +

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

What risk level is signavio_move_model? +

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

Can I rate-limit signavio_move_model? +

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

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

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

Enforce policy on every Signavio MCP Server tool call.

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.

CHECK YOUR STACK →