save_global_df | PolicyLayer

WHAT IT DOES

What save_global_df does on Vibe Preprocessing and Analysis MCP Server

AI agents use save_global_df to create or update resources in Vibe Preprocessing and Analysis MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vibe Preprocessing and Analysis MCP Server environment.

WHY IT NEEDS A POLICY

Why save_global_df needs a policy

The tool writes data to disk (create/modify operation). It is reversible (files can be deleted or overwritten), so it does not qualify as Destructive. The severity is medium because an agent could inadvertently overwrite existing files or generate large volumes of data in the work directory, potentially consuming storage or overwriting important analysis results.

From the tool's definition Tool description states 'Save the current global DataFrame to a file in the WORK_DIR' — this creates or persists data to storage.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

save_global_df Rate-limited

save_global_df 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": {
    "save_global_df": {
      "limits": [
        {
          "counter": "save_global_df_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 Vibe Preprocessing and Analysis MCP Server, so you can run agents against it safely.

FAQ

Questions about save_global_df

What does the save_global_df tool do? +

Save the current global DataFrame to a file in the WORK_DIR. It is categorised as a Write tool in the Vibe Preprocessing and Analysis 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 save_global_df? +

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

What risk level is save_global_df? +

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

Can I rate-limit save_global_df? +

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

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

save_global_df is provided by the Vibe Preprocessing and Analysis MCP Server MCP server (mudit14224/vibe-data-analysis). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.