save_as

THE RISK

Medium Risk

Why save_as needs a policy

This tool creates or modifies files on the filesystem by saving BPMN diagram data with a new filename. It is Write rather than Destructive because it does not irreversibly delete data—the operation is reversible and the original file typically remains intact.

From the tool's definition Tool name 'save_as' and description 'Save the current diagram with a new filename' indicate file creation/modification. The BPMN server context shows this tool persists diagrams to storage, creating or overwriting files.

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

POLICY

How to control save_as

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-BPMN Server, and nothing reaches the server without passing your rules. This is the rule we recommend for save_as:

policy.json

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

save_as 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 MCP-BPMN 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 MCP-BPMN Server tools

Destructive bpmn_delete_diagram Delete a saved BPMN diagram file Destructive bpmn_delete_element Delete an element from the process Destructive delete_diagram_file Delete a saved BPMN diagram file Destructive delete_element Delete an element from the current diagram Write new_bpmn Create a new BPMN diagram and set it as current context Write new_from_mermaid Create a new BPMN diagram from Mermaid code and set it as current context Write add_activity Add an activity to the current diagram Write add_event Add an event to the current diagram

All 41 MCP-BPMN 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 save_as

What does the save_as tool do? +

Save the current diagram with a new filename. It is categorised as a Write tool in the MCP-BPMN 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 save_as? +

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

What risk level is save_as? +

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

Can I rate-limit save_as? +

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

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

save_as is provided by the MCP-BPMN Server MCP server (oisee/mcp-bpmn). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP-BPMN Server tool call.

Start from MCP-BPMN Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →