check_and_save · Virtuoso Schematic MCP: Risk & Policy

WHAT IT DOES

What check_and_save does on Virtuoso Schematic MCP

AI agents invoke check_and_save to trigger actions in Virtuoso Schematic MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why check_and_save needs a policy

This tool executes two distinct operations: a schematic design rule/validation check (schCheck) and a database save (dbSave). The save operation modifies persistent design files on disk, and the check triggers an external tool execution. Together these constitute an Execute-level action with Write side effects. Misuse could overwrite schematic state or corrupt design data, warranting high severity.

From the tool's definition 'Run schCheck and dbSave on the schematic' — executes schematic check (schCheck) and saves the design (dbSave), triggering external EDA operations

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

check_and_save Rate-limited

check_and_save stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_and_save": {
      "limits": [
        {
          "counter": "check_and_save_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about check_and_save

What does the check_and_save tool do? +

Run schCheck and dbSave on the schematic. It is categorised as a Execute tool in the Virtuoso Schematic MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on check_and_save? +

Register the Virtuoso Schematic MCP server in PolicyLayer and add a rule for check_and_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 Virtuoso Schematic MCP. Nothing to install.

What risk level is check_and_save? +

check_and_save is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit check_and_save? +

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

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

check_and_save is provided by the Virtuoso Schematic MCP server (michelebergo/virtuoso-schematic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.