upload_media_from_path
Upload a local file (on the nexus host) to the Card Builder media directory.
This record as markdown: /tools/fistacho-ha-nexus-agent/upload-media-from-path.md
What upload_media_from_path does on Ha Nexus Agent
AI agents use upload_media_from_path 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.
Why upload_media_from_path is rated Medium
Uploading a file is a reversible write operation (files can be deleted). While it creates new data in the system, it does not irreversibly destroy anything and does not execute arbitrary code or move money.
From the tool's definition Tool description states 'Upload a local file... to the Card Builder media directory' — this creates/adds a file to a destination directory, which is a write operation that modifies the media storage state.
Attacks that exploit this kind of access
The rule that runs upload_media_from_path 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_from_path, this is the rule to start with:
upload_media_from_path 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 Ha Nexus Agent, apply this rule, and every upload_media_from_path call is checked against it from then on.
Questions about upload_media_from_path
Upload a local file (on the nexus host) 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.
Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for upload_media_from_path: 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.
upload_media_from_path 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_media_from_path 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_media_from_path. 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_media_from_path 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.
More on Ha Nexus Agent, and thousands of servers like it.
This server
Across the catalogue