delete_metric

Delete one metric definition by its id.

Server Querywise kosminus/querywise-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_metric does on Querywise

AI agents call delete_metric to permanently remove resources in Querywise — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_metric needs a policy

Metric definitions are configuration artifacts that, once deleted, cannot be recovered without manual recreation. This action is irreversible and could disrupt business logic, reports, and AI agent queries that depend on that metric. While the blast radius is narrower than data deletion, it is destructive in nature.

From the tool's definition Tool name explicitly states 'delete_metric' and description confirms 'Delete one metric definition by its id' — this irreversibly removes a metric definition from the knowledge base.

Questions about delete_metric

What does the delete_metric tool do? +

Delete one metric definition by its id. It is categorised as a Destructive tool in the Querywise MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_metric? +

Register the Querywise MCP server in PolicyLayer and add a rule for delete_metric: 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 Querywise. Nothing to install.

What risk level is delete_metric? +

delete_metric is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_metric? +

Yes. Add a rate_limit block to the delete_metric 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.

How do I block delete_metric completely? +

Set action: deny in the PolicyLayer policy for delete_metric. 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.

What MCP server provides delete_metric? +

delete_metric is provided by the Querywise MCP server (kosminus/querywise-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

delete_metric is one line of Querywise's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.