AI agents use resolve_conflicts to create or update resources in NPM Helper MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your NPM Helper MCP environment.
This tool modifies project dependency configurations reversibly (changes can be undone by reverting files or re-running resolution). While it affects the codebase, the changes are not permanent deletions and can be rolled back. The incomplete description ('uses' cuts off) lowers confidence slightly, but the context from sibling tools and the nature of conflict resolution strongly indicates Write semantics.
From the tool's definition 'resolve_conflicts' handles dependency conflicts, which typically involves modifying package.json or lock files to update version constraints and dependencies.
Documented attack patterns abuse exactly the kind of access resolve_conflicts gives an agent:
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 resolve_conflicts:
{
"version": "1",
"default": "deny",
"tools": {
"resolve_conflicts": {
"limits": [
{
"counter": "resolve_conflicts_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}resolve_conflicts stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Handle dependency conflicts (uses. It is categorised as a Write tool in the NPM Helper MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the NPM Helper MCP server in PolicyLayer and add a rule for resolve_conflicts: 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.
resolve_conflicts is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the resolve_conflicts 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 resolve_conflicts. 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.
resolve_conflicts 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.
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.
Free to start. No card required.
10 NPM Helper MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.