Clear stored network request logs
AI agents call clear_network_logs to permanently remove resources in InSite — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing logs is irreversible — once network request logs are deleted, they cannot be recovered. However, the blast radius is low since only diagnostic/logging data is lost, not production data or system state.
From the tool's definition Clear stored network request logs
Attacks that exploit this kind of access
Clear stored network request logs. It is categorised as a Destructive tool in the InSite MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the InSite MCP server in PolicyLayer and add a rule for clear_network_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 InSite. Nothing to install.
clear_network_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_network_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_network_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_network_logs is provided by the InSite MCP server (jowharshamshiri/insite). 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 →