upload_site_asset
Store an image/asset under the site
This record as markdown: /tools/ai-featureboard-featureboard/upload-site-asset.md
What upload_site_asset does on FeatureBoard
AI agents use upload_site_asset 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 upload_site_asset is rated Medium
This tool creates or modifies data (image/asset storage) in a reversible manner. It does not delete, execute code, or move money, so it falls under Write rather than more severe categories. Severity is medium because malicious asset uploads could deface a site, introduce malware links, or consume storage resources, but the impact is generally contained to the asset store itself.
From the tool's definition The tool description states 'Store an image/asset under the site', which indicates creation or modification of assets in a file storage system.
Attacks that exploit this kind of access
The rule that runs upload_site_asset 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 upload_site_asset, this is the rule to start with:
upload_site_asset 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 upload_site_asset call is checked against it from then on.
Questions about upload_site_asset
Store an image/asset under the site. 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 upload_site_asset: 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.
upload_site_asset 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 upload_site_asset 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 upload_site_asset. 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.
upload_site_asset 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