rc_save · RC Engine MCP: Risk & Policy

WHAT IT DOES

What rc_save does on RC Engine

AI agents use rc_save to create or update resources in RC Engine — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RC Engine environment.

WHY IT NEEDS A POLICY

Why rc_save needs a policy

This tool writes/saves data to a file structure, which is a reversible modification operation. It does not execute arbitrary code, delete data, or move financial resources. While it modifies the RC Method file structure, the operation is not destructive and appears to be part of normal artifact management workflow.

From the tool's definition Tool name 'rc_save' and description 'Save an artifact generated by the host IDE...into the RC Method file structure' explicitly indicates creating or modifying data by persisting artifacts into a structured system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rc_save Rate-limited

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

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches RC Engine, so you can run agents against it safely.

FAQ

Questions about rc_save

What does the rc_save tool do? +

PASSTHROUGH MODE ONLY. Save an artifact generated by the host IDE (not by RC Engine tools) into the RC Method file structure. Use when the IDE\. It is categorised as a Write tool in the RC Engine MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rc_save? +

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

What risk level is rc_save? +

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

Can I rate-limit rc_save? +

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

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

rc_save is provided by the RC Engine MCP server (originalrashmi/rc-engine-product-framework). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.