This record as markdown: /tools/io-github-dave-london-npm/webpack.md
What webpack does on Npm
AI agents invoke webpack to trigger actions in Npm. 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 webpack is rated High
This is an Execute category tool because it triggers webpack, a complex build system that runs code execution during the bundling process. An AI agent could abuse this to execute malicious code if webpack configuration files or dependencies are compromised, or if the tool accepts config parameters.
From the tool's definition Tool explicitly 'Runs webpack build' which executes an external build system. Webpack is a JavaScript bundler that processes code, executes transformations, and can invoke arbitrary scripts defined in webpack config files and npm lifecycle hooks.
Attacks that exploit this kind of access
The rule that runs webpack safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Npm, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For webpack, this is the rule to start with:
webpack 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 Npm, apply this rule, and every webpack call is checked against it from then on.
Questions about webpack
Runs webpack build with JSON stats output and returns structured assets, errors, and warnings. It is categorised as a Execute tool in the Npm MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Npm MCP server in PolicyLayer and add a rule for webpack: 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 Npm. Nothing to install.
webpack 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 webpack 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 webpack. 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.
webpack is provided by the Npm MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Npm, and thousands of servers like it.
This server
Across the catalogue