reload_extensions
Reload plugins and workflows from configured directories, and directly register extension tools visible in the current profile.
This record as markdown: /tools/io-github-vmoranv-jshookmcp/reload-extensions.md
What reload_extensions does on Jshookmcp
AI agents invoke reload_extensions to trigger actions in Jshookmcp. 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 reload_extensions is rated High
Reloading and registering extensions triggers external operations that modify the active tool environment.
From the tool's definition Reload plugins and workflows, directly register extension tools
Attacks that exploit this kind of access
The rule that runs reload_extensions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reload_extensions, this is the rule to start with:
reload_extensions 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every reload_extensions call is checked against it from then on.
Questions about reload_extensions
Reload plugins and workflows from configured directories, and directly register extension tools visible in the current profile. It is categorised as a Execute tool in the Jshookmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Jshook MCP server in PolicyLayer and add a rule for reload_extensions: 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 Jshookmcp. Nothing to install.
reload_extensions is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the reload_extensions 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 reload_extensions. 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.
reload_extensions is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Jshook, and thousands of servers like it.
Across the catalogue