filter_updates

THE RISK

High Risk

Why filter_updates needs a policy

The description is ambiguous ('Check/upgrade'), but the 'upgrade' aspect implies it can modify the project's installed packages, not merely read. Upgrading dependencies is a Write/Execute action that changes the project state.

From the tool's definition 'Check/upgrade updates for specific packages' — the tool both checks AND upgrades packages, meaning it can actively modify installed dependencies

Documented attack patterns abuse exactly the kind of access filter_updates gives an agent:

POLICY

How to control filter_updates

PolicyLayer is an MCP gateway — it sits between your AI agents and NPM Helper MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for filter_updates:

policy.json

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

filter_updates 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.

Create a free account and register NPM Helper MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More NPM Helper MCP tools

Execute run_doctor Iteratively install upgrades and run tests Write upgrade_packages Upgrade dependencies in package.json Write resolve_conflicts Handle dependency conflicts (uses Write set_version_constraints Configure version upgrade rules for dependencies Read check_updates Scan package.json for outdated dependencies Read fetch_package_content Fetch detailed content from an npm package page URL Read get_package_details Get detailed information about an npm package Read get_package_versions Get available versions for an npm package

All 10 NPM Helper MCP tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in NPM Helper MCP → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about filter_updates

What does the filter_updates tool do? +

Check/upgrade updates for specific packages. It is categorised as a Execute tool in the NPM Helper MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on filter_updates? +

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

What risk level is filter_updates? +

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

Can I rate-limit filter_updates? +

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

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

filter_updates is provided by the NPM Helper MCP server (pinkpixel-dev/npm-helper-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every NPM Helper MCP tool call.

Start from NPM Helper MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →