upload_media

Upload a file to the Card Builder media directory.

SERVERHa Nexus Agent SOURCEfistacho/ha-nexus-agent

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/fistacho-ha-nexus-agent/upload-media.md

WHAT IT DOES

What upload_media does on Ha Nexus Agent

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

RISK

Why upload_media is rated Medium

This tool writes data to a persistent storage location (media directory), modifying the state of the Home Assistant server by adding new files. While not destructive (files can be deleted), it is a write operation that could be leveraged to store malicious payloads, configuration files, or other unwanted content in a smart home system.

From the tool's definition 'Upload a file to the Card Builder media directory' — the tool creates/adds files to a system directory.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs upload_media safely

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

upload_media Rate-limited

upload_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": {
    "upload_media": {
      "limits": [
        {
          "counter": "upload_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 Ha Nexus Agent, apply this rule, and every upload_media call is checked against it from then on.

FAQ

Questions about upload_media

What does the upload_media tool do? +

Upload a file to the Card Builder media directory. It is categorised as a Write tool in the Ha Nexus Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on upload_media? +

Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for upload_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 Ha Nexus Agent. Nothing to install.

What risk level is upload_media? +

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

Can I rate-limit upload_media? +

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

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

upload_media is provided by the Ha Nexus Agent MCP server (fistacho/ha-nexus-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ha Nexus Agent, and thousands of servers like it.

This server

All 276 Ha Nexus Agent tools →

Across the catalogue

The MCP Attack Database →

Guides

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