resolve_error
Map error OR free-text query to a verified fix. USE WHEN: user pastes a concrete error/stack (ENOENT, ImportError, build failure) — pass error. OR user describes a symptom ('webpack slow', 'pip stuck') — pass query. Always prefer this over guessing a fix. RETURNS: exact-match {status, solution, c...
This record as markdown: /tools/dev-depscope-mcp/resolve-error.md
What resolve_error does on Depscope
AI agents call resolve_error 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 |
|---|---|---|---|
error | string | — | Concrete error message / stack trace. Triggers exact-match lookup. |
limit | integer | — | Max search results (query mode only). |
query | string | — | Free-text symptom description. Triggers KB search. |
context | object | — | Optional context for error-mode calls (ecosystem, package, version). |
Parameters from the server's own tool schema.
Why resolve_error is rated Low
The tool looks up and retrieves solutions/fixes for errors or queries. It performs a read/lookup operation returning informational results with no side effects, data modification, or execution of code.
From the tool's definition Map error OR free-text query to a verified fix... RETURNS: exact-match {status, solution, confidence, source_url} or search results [{title, summary, source_url}]
Attacks that exploit this kind of access
The rule that runs resolve_error 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 resolve_error, this is the rule to start with:
resolve_error 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 resolve_error call is checked against it from then on.
Questions about resolve_error
Map error OR free-text query to a verified fix. USE WHEN: user pastes a concrete error/stack (ENOENT, ImportError, build failure) — pass error. OR user describes a symptom ('webpack slow', 'pip stuck') — pass query. Always prefer this over guessing a fix. RETURNS: exact-match {status, solution, confidence, source_url} or search results [{title, summary, source_url}]. It is categorised as a Read tool in the Depscope MCP Server, which means it retrieves data without modifying state.
resolve_error accepts 4 parameters: error, limit, query, context. 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 resolve_error: 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.
resolve_error 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 resolve_error 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_error. 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_error 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