clear-audit-log

Clear all audit log entries

SERVERFrontmcp SOURCEagentfront/frontmcp

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/frontmcp/clear-audit-log.md

WHAT IT DOES

What clear-audit-log does on Frontmcp

AI agents call clear-audit-log to permanently remove resources in Frontmcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why clear-audit-log is rated Critical

Audit logs are critical for security, compliance, and accountability. Irreversibly deleting all audit log entries prevents forensic investigation, violates compliance requirements (SOX, HIPAA, GDPR, etc.), and could hide unauthorized activity. This is a destructive operation with high blast radius if misused by an AI agent.

From the tool's definition Tool name 'clear-audit-log' with description 'Clear all audit log entries' indicates irreversible deletion of audit records. The verb 'clear' in combination with 'all' entries confirms destructive intent.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs clear-audit-log safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clear-audit-log, this is the rule to start with:

clear-audit-log Hidden

clear-audit-log is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "clear-audit-log"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Frontmcp, apply this rule, and every clear-audit-log call is checked against it from then on.

FAQ

Questions about clear-audit-log

What does the clear-audit-log tool do? +

Clear all audit log entries. It is categorised as a Destructive tool in the Frontmcp 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-audit-log? +

Register the Front MCP server in PolicyLayer and add a rule for clear-audit-log: 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 Frontmcp. Nothing to install.

What risk level is clear-audit-log? +

clear-audit-log 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-audit-log? +

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

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

clear-audit-log is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Front, and thousands of servers like it.

This server

All 206 Front tools → Critical-risk tools on this server →

Across the catalogue

clear_renders on Why Did You Render →knowledge_clear on Templonix Lite MCP Server →clear_scan on Frida Game Hacking MCP →clear_spam_box on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →