import_file

A write tool on the Aos MCP server.

SERVERAos SOURCE@hybridlabor-api/aos

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/hybridlabor-api-aos/import-file.md

WHAT IT DOES

What import_file does on Aos

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

RISK

Why import_file is rated Medium

Import operations load and integrate external files into the Blender project, modifying the scene state reversibly. While the description is empty (lowering confidence slightly), the name and context of sibling Write operations (add_*) suggest this creates or modifies Blender project data.

From the tool's definition Tool name 'import_file' indicates loading external data into Blender; sibling tools like 'add_bone', 'add_modifier', 'add_constraint' are Write operations that create/modify project state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs import_file safely

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

import_file Rate-limited

import_file 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": {
    "import_file": {
      "limits": [
        {
          "counter": "import_file_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 Aos, apply this rule, and every import_file call is checked against it from then on.

FAQ

Questions about import_file

What does the import_file tool do? +

import_file is a write tool on the Aos MCP server. It is categorised as a Write tool in the Aos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on import_file? +

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

What risk level is import_file? +

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

Can I rate-limit import_file? +

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

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

import_file is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Aos, and thousands of servers like it.

This server

All 719 Aos tools →

Across the catalogue

write_file on 0sec → The MCP Attack Database →

Guides

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