delete_custom_metric
AI agents call delete_custom_metric to permanently remove resources in Ai Analyst — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The delete_ prefix signals a destructive operation that cannot be undone. Deleting a custom metric removes a configuration or definition that users have created, which is irreversible. Although the description is empty (lowering confidence slightly from critical to high), the tool name itself unambiguously indicates a destructive action.
From the tool's definition Tool name is 'delete_custom_metric' which explicitly indicates deletion/removal of a custom metric definition. The 'delete' verb combined with 'custom_metric' indicates irreversible removal of data.
Attacks that exploit this kind of access
delete_custom_metric. It is categorised as a Destructive tool in the Ai Analyst MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ai Analyst MCP server in PolicyLayer and add a rule for delete_custom_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 Ai Analyst. Nothing to install.
delete_custom_metric 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 delete_custom_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.
Set action: deny in the PolicyLayer policy for delete_custom_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.
delete_custom_metric is provided by the Ai Analyst MCP server (sbdk-dev/local-ai-analyst). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →