webpack
Runs webpack build with JSON stats output and returns structured assets, errors, and warnings.
This record as markdown: /tools/io-github-dave-london-build/webpack.md
What webpack does on Build
AI agents invoke webpack to trigger actions in Build. 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
While the tool primarily produces build artifacts (which might suggest Write category), the act of running webpack inherently involves executing arbitrary code - webpack configurations, plugins, and loaders execute JavaScript in the build environment. This execution can trigger side effects beyond simple data creation (network requests, file system operations, environment variable access, subprocess spawning).
From the tool's definition Tool description states "Runs webpack build" - webpack is a module bundler that executes JavaScript code during the build process, including arbitrary user code in webpack configuration files and loaders.
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 Build, 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 Build, 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 Build MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Build 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 Build. 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 Build 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 Build, and thousands of servers like it.
Across the catalogue