sourcemaps_resolve
Resolve a compiled line:col against the stored source map for app+version. Returns {source, line, column, name} or an error when the map is missing.
This record as markdown: /tools/io-github-kivanccakmak-yaver/sourcemaps-resolve.md
What sourcemaps_resolve does on Yaver
AI agents call sourcemaps_resolve to retrieve information from Yaver 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 |
|---|---|---|---|
app | string | Yes | |
line | integer | Yes | |
column | integer | Yes | |
version | string | Yes |
Parameters from the server's own tool schema.
Why sourcemaps_resolve is rated Low
This tool purely queries/reads source map data to resolve a compiled location back to its original source coordinates. It has no side effects, does not modify any data, and only returns lookup results.
From the tool's definition Resolve a compiled line:col against the stored source map for app+version. Returns {source, line, column, name} or an error when the map is missing.
Attacks that exploit this kind of access
The rule that runs sourcemaps_resolve safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sourcemaps_resolve, this is the rule to start with:
sourcemaps_resolve 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 Yaver, apply this rule, and every sourcemaps_resolve call is checked against it from then on.
Questions about sourcemaps_resolve
Resolve a compiled line:col against the stored source map for app+version. Returns {source, line, column, name} or an error when the map is missing. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
sourcemaps_resolve accepts 4 parameters: app, line, column, version. Required: app, line, column, version. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for sourcemaps_resolve: 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 Yaver. Nothing to install.
sourcemaps_resolve 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 sourcemaps_resolve 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 sourcemaps_resolve. 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.
sourcemaps_resolve is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue