reload_api · Inventor MCP: Risk & Policy

WHAT IT DOES

What reload_api does on Inventor

AI agents invoke reload_api to trigger actions in Inventor. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why reload_api needs a policy

This tool dynamically reloads a Python API module from disk at runtime, which is a code execution operation. It triggers the loading and execution of potentially modified Python code, making it an Execute-category action. Misuse could allow arbitrary code execution by swapping the module on disk before reload, giving it high severity.

From the tool's definition Hot-reload inventor_api.py from disk. Use after editing the wrapper

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reload_api Rate-limited

reload_api stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "reload_api": {
      "limits": [
        {
          "counter": "reload_api_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Inventor, so you can run agents against it safely.

FAQ

Questions about reload_api

What does the reload_api tool do? +

Hot-reload inventor_api.py from disk. Use after editing the wrapper —. It is categorised as a Execute tool in the Inventor MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on reload_api? +

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

What risk level is reload_api? +

reload_api is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit reload_api? +

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

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

reload_api is provided by the Inventor MCP server (neonglay/inventor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.