Clear log buffer and files
AI agents call clear_logs to permanently remove resources in Gradle Tomcat MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes log files and buffers, which is an irreversible operation. Log data is critical for debugging, auditing, compliance, and forensic analysis. Once cleared, the logs cannot be recovered. This fits the Destructive category as the action cannot be undone. Severity is high because loss of logs can impact system observability, security incident investigation, and regulatory compliance.
From the tool's definition Tool name 'clear_logs' and description 'Clear log buffer and files' indicates irreversible deletion of log data. The word 'clear' combined with 'log buffer and files' means data cannot be recovered once executed.
Attacks that exploit this kind of access
Clear log buffer and files. It is categorised as a Destructive tool in the Gradle Tomcat MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Gradle Tomcat MCP Server MCP server in PolicyLayer and add a rule for clear_logs: 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 Gradle Tomcat MCP Server. Nothing to install.
clear_logs 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 clear_logs 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 clear_logs. 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.
clear_logs is provided by the Gradle Tomcat MCP Server MCP server (lkb2k/mcp-gradle). 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 →