This record as markdown: /tools/io-github-dave-london-git/rollup.md
What rollup does on Git
AI agents invoke rollup to trigger actions in Git. 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 rollup is rated High
The tool runs an external build process (Rollup bundler), which constitutes executing code/external operations. While it primarily produces output artifacts, running a bundler can execute arbitrary plugins, scripts, and transformations defined in config files, making it an Execute-category action. Severity is medium as misuse could execute malicious build scripts but is generally scoped to the project environment.
From the tool's definition 'Runs Rollup bundler' — actively executes the Rollup build tool, triggering external operations
Attacks that exploit this kind of access
The rule that runs rollup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Git, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rollup, this is the rule to start with:
rollup 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 Git, apply this rule, and every rollup call is checked against it from then on.
Questions about rollup
Runs Rollup bundler and returns structured bundle output with errors and warnings. It is categorised as a Execute tool in the Git MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Git MCP server in PolicyLayer and add a rule for rollup: 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 Git. Nothing to install.
rollup 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 rollup 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 rollup. 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.
rollup is provided by the Git 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 Git, and thousands of servers like it.
This server
Across the catalogue