resetToolTelemetry

THE RISK

Critical Risk

Why resetToolTelemetry needs a policy

Resetting telemetry irreversibly destroys accumulated performance data. While not destructive in terms of financial or system damage, the rolling telemetry data cannot be recovered once reset, making this a Destructive action. Severity is medium since telemetry/monitoring data loss can impair observability but doesn't affect core system functionality.

From the tool's definition Reset rolling performance telemetry for one tool or all tools

Documented attack patterns abuse exactly the kind of access resetToolTelemetry gives an agent:

POLICY

How to control resetToolTelemetry

PolicyLayer is an MCP gateway — it sits between your AI agents and Ltspice, and nothing reaches the server without passing your rules. This is the rule we recommend for resetToolTelemetry:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "resetToolTelemetry"
  ]
}

resetToolTelemetry disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Ltspice — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Ltspice tools

Destructive endLtspiceRenderSession Close the LTspice window associated with a render session. Execute cancelJob Request cancellation for a queued/running job. Execute daemonDoctor Run a daemon/system health check and return actionable recommendations. Execute runMeasAutomation Inject .meas directives into a netlist, run simulation, and parse measurement values. Execute runSimulation Run LTspice in batch mode for the currently loaded netlist. Execute runSweepStudy runSweepStudy Execute runVerificationPlan runVerificationPlan Execute simulateNetlist Write a netlist and run LTspice batch simulation in one call.

All 71 Ltspice tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Ltspice → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about resetToolTelemetry

What does the resetToolTelemetry tool do? +

Reset rolling performance telemetry for one tool or all tools. It is categorised as a Destructive tool in the Ltspice 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 resetToolTelemetry? +

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

What risk level is resetToolTelemetry? +

resetToolTelemetry 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 resetToolTelemetry? +

Yes. Add a rate_limit block to the resetToolTelemetry 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 resetToolTelemetry completely? +

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

resetToolTelemetry is provided by the Ltspice MCP server (xuio/ltspice-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ltspice tool call.

Start from Ltspice, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →