reset_mcp_runtime_metrics
Reset MCP runtime transport metrics counters.
This record as markdown: /tools/0xpdf-mcp/reset-mcp-runtime-metrics.md
What reset_mcp_runtime_metrics does on 0xpdf
AI agents call reset_mcp_runtime_metrics to permanently remove resources in 0xpdf, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why reset_mcp_runtime_metrics is rated Critical
An AI agent that decides to call reset_mcp_runtime_metrics doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from 0xpdf is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs reset_mcp_runtime_metrics safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0xpdf, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reset_mcp_runtime_metrics, this is the rule to start with:
reset_mcp_runtime_metrics 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 0xpdf, apply this rule, and every reset_mcp_runtime_metrics call is checked against it from then on.
Questions about reset_mcp_runtime_metrics
Reset MCP runtime transport metrics counters. It is categorised as a Destructive tool in the 0xpdf MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the 0xpdf MCP server in PolicyLayer and add a rule for reset_mcp_runtime_metrics: 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 0xpdf. Nothing to install.
reset_mcp_runtime_metrics 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 reset_mcp_runtime_metrics 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 reset_mcp_runtime_metrics. 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.
reset_mcp_runtime_metrics is provided by the 0xpdf MCP server (risha-max/0xpdf-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0xpdf, and thousands of servers like it.
Across the catalogue