save_media

Save a generated asset into a project

SERVERFeatureBoard SOURCEhttps://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-featureboard-featureboard/save-media.md

WHAT IT DOES

What save_media does on FeatureBoard

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

RISK

Why save_media is rated Medium

This tool creates or adds new media assets to a project, which is a reversible write operation. It does not execute arbitrary code, delete data irreversibly, or move money. The severity is medium because misuse could clutter or bloat a project with unwanted generated assets, but the impact is localized to media storage and reversible via deletion.

From the tool's definition Tool description states 'Save a generated asset into a project' — a create/store operation that modifies project state by persisting media files.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs save_media safely

PolicyLayer is an MCP gateway: it sits between your AI agents and FeatureBoard, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For save_media, this is the rule to start with:

save_media Rate-limited

save_media 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_media": {
      "limits": [
        {
          "counter": "save_media_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FeatureBoard, apply this rule, and every save_media call is checked against it from then on.

FAQ

Questions about save_media

What does the save_media tool do? +

Save a generated asset into a project. It is categorised as a Write tool in the FeatureBoard 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_media? +

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

What risk level is save_media? +

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

Can I rate-limit save_media? +

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

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

save_media is provided by the FeatureBoard MCP server (https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on FeatureBoard, and thousands of servers like it.

This server

All 215 FeatureBoard tools →

Across the catalogue

save_snapshot on Why Did You Render → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →