check_compatibility
Is this specific multi-package version combo verified to work together? USE WHEN: pinning a stack (next@15 + react@19 + node@22); before recommending a version matrix. RETURNS: {compatible, conflicts[], notes}.
This record as markdown: /tools/dev-depscope-mcp/check-compatibility.md
What check_compatibility does on Depscope
AI agents call check_compatibility 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 |
|---|---|---|---|
packages | object | Yes | Package -> version map, e.g. {"next":"15","react":"19"}. |
Parameters from the server's own tool schema.
Why check_compatibility is rated Low
This tool queries a compatibility database to verify whether specific package version combinations work together. It retrieves information and provides analysis but does not install, modify, delete, execute code, or trigger external side effects. The use case (pinning a stack, recommending a version matrix) confirms it serves a verification/query function. No reversible or irreversible data modification occurs.
From the tool's definition Tool description indicates it 'checks' and 'returns' compatibility data without modifying any packages, dependencies, or external state.
Attacks that exploit this kind of access
The rule that runs check_compatibility 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 check_compatibility, this is the rule to start with:
check_compatibility 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 check_compatibility call is checked against it from then on.
Questions about check_compatibility
Is this specific multi-package version combo verified to work together? USE WHEN: pinning a stack (next@15 + react@19 + node@22); before recommending a version matrix. RETURNS: {compatible, conflicts[], notes}. It is categorised as a Read tool in the Depscope MCP Server, which means it retrieves data without modifying state.
check_compatibility accepts 1 parameter: packages. Required: packages. 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 check_compatibility: 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.
check_compatibility 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 check_compatibility 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 check_compatibility. 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.
check_compatibility 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