save_packaging_config
Persist the .mcpb packaging metadata for a project (packaging.json): name (slugified), displayName, description, longDescription, keywords, version. Validated by the same rules the build preflight uses; rejects hard errors (missing name/description). Only provided fields change.
This record as markdown: /tools/ai-featureboard-featureboard/save-packaging-config.md
What save_packaging_config does on FeatureBoard
AI agents use save_packaging_config 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.
Why save_packaging_config is rated Medium
This tool modifies project configuration files (packaging.json) by persisting metadata fields. This is a Write operation because it changes data reversibly without deleting or executing arbitrary code. While the blast radius is medium (misconfigured packaging could affect project distribution/CI), it is not Execute (no code execution) or Destructive (changes are reversible).
From the tool's definition 'Persist the .mcpb packaging metadata for a project (packaging.json)' and 'Only provided fields change' indicate modification of configuration data. The tool creates or updates project packaging metadata in a reversible manner.
Attacks that exploit this kind of access
The rule that runs save_packaging_config 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_packaging_config, this is the rule to start with:
save_packaging_config 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.
The button opens the PolicyLayer dashboard: create your workspace, connect FeatureBoard, apply this rule, and every save_packaging_config call is checked against it from then on.
Questions about save_packaging_config
Persist the .mcpb packaging metadata for a project (packaging.json): name (slugified), displayName, description, longDescription, keywords, version. Validated by the same rules the build preflight uses; rejects hard errors (missing name/description). Only provided fields change. 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.
Register the FeatureBoard MCP server in PolicyLayer and add a rule for save_packaging_config: 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.
save_packaging_config is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the save_packaging_config 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.
Set action: deny in the PolicyLayer policy for save_packaging_config. 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.
save_packaging_config 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.
More on FeatureBoard, and thousands of servers like it.
This server
Across the catalogue