sourcemaps_delete
Remove the source map for a specific app + version tuple. Destructive.
This record as markdown: /tools/io-github-kivanccakmak-yaver/sourcemaps-delete.md
What sourcemaps_delete does on Yaver
AI agents call sourcemaps_delete to permanently remove resources in Yaver, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
app | string | Yes | |
version | string | Yes |
Parameters from the server's own tool schema.
Why sourcemaps_delete is rated Critical
This tool irreversibly deletes source map files associated with a specific app and version. Source maps are critical debugging and development artifacts; their deletion cannot be easily undone and removes important development context. The description explicitly marks it as destructive, confirming the category.
From the tool's definition Tool name 'sourcemaps_delete' combined with explicit description stating 'Remove the source map for a specific app + version tuple. Destructive.' The description directly labels this as a destructive operation.
Attacks that exploit this kind of access
The rule that runs sourcemaps_delete 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_delete, this is the rule to start with:
sourcemaps_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every sourcemaps_delete call is checked against it from then on.
Questions about sourcemaps_delete
Remove the source map for a specific app + version tuple. Destructive. It is categorised as a Destructive tool in the Yaver MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
sourcemaps_delete accepts 2 parameters: app, version. Required: app, 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_delete: 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_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the sourcemaps_delete 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_delete. 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_delete 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.
Across the catalogue