get_breaking_changes
Breaking changes between two majors of the SAME package (next@14→15). USE WHEN: user is bumping a major; before recommending a major upgrade. Different from get_migration_path (same pkg vs. different pkg). RETURNS: {breaking_changes[]: {area, description, hint}}.
This record as markdown: /tools/dev-depscope-mcp/get-breaking-changes.md
What get_breaking_changes does on Depscope
AI agents call get_breaking_changes to retrieve information from Depscope without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
package | string | Yes | |
ecosystem | string | Yes | |
to_version | string | — | |
from_version | string | — |
Parameters from the server's own tool schema.
Why get_breaking_changes is rated Low
This is a read-only query tool that retrieves and presents comparative metadata about package versions. It helps users understand upgrade impacts but does not execute code, modify dependencies, delete data, or commit resources. The low severity reflects minimal blast radius if misused by an AI agent—worst case is receiving incorrect or misleading breaking-change information, not system compromise or data loss.
From the tool's definition Tool description explicitly states it RETURNS breaking changes data without modifying any package, dependency, or system state. The verb 'RETURNS' and the stated use case ('before recommending') indicate pure information retrieval.
Attacks that exploit this kind of access
The rule that runs get_breaking_changes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Depscope, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_breaking_changes, this is the rule to start with:
get_breaking_changes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Depscope, apply this rule, and every get_breaking_changes call is checked against it from then on.
Questions about get_breaking_changes
Breaking changes between two majors of the SAME package (next@14→15). USE WHEN: user is bumping a major; before recommending a major upgrade. Different from get_migration_path (same pkg vs. different pkg). RETURNS: {breaking_changes[]: {area, description, hint}}. It is categorised as a Read tool in the Depscope MCP Server, which means it retrieves data without modifying state.
get_breaking_changes accepts 4 parameters: package, ecosystem, to_version, from_version. Required: package, ecosystem. The full parameter table on this page comes from the server's own tool schema.
Register the Depscope MCP server in PolicyLayer and add a rule for get_breaking_changes: 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 Depscope. Nothing to install.
get_breaking_changes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_breaking_changes 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 get_breaking_changes. 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.
get_breaking_changes is provided by the Depscope MCP server (cuttalo/depscope-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Depscope, and thousands of servers like it.
This server
Across the catalogue