New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

clear_failed_requests

Drain the dead-letter queue. Returns the number of entries removed. Use after manually replaying or after resolving the upstream issue.

SERVERMax MCP Server SOURCEdigital-crew-technologies/max-mcp-server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/digital-crew-technologies-max-mcp-server/clear-failed-requests.md

What clear_failed_requests does on Max MCP Server

AI agents call clear_failed_requests to permanently remove resources in Max MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why clear_failed_requests is rated Critical

The tool irreversibly removes all entries from the dead-letter queue. Once drained, those failed request records are gone and cannot be replayed or recovered, making this a destructive action. Misuse could cause permanent loss of pending operations that were awaiting retry or manual replay.

From the tool's definition 'Drain the dead-letter queue' and 'number of entries removed' — permanently removes queued entries that cannot be recovered after clearing

Questions about clear_failed_requests

What does the clear_failed_requests tool do? +

Drain the dead-letter queue. Returns the number of entries removed. Use after manually replaying or after resolving the upstream issue. It is categorised as a Destructive tool in the Max MCP Server 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 clear_failed_requests? +

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

What risk level is clear_failed_requests? +

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

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

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

clear_failed_requests is provided by the Max MCP Server MCP server (digital-crew-technologies/max-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Max MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Max MCP Server's. Pull the full record:

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.