proxy_clear_logs

Clear all captured proxy request/response logs.

SERVERJshookmcp SOURCE@jshookmcp/jshook

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/io-github-vmoranv-jshookmcp/proxy-clear-logs.md

WHAT IT DOES

What proxy_clear_logs does on Jshookmcp

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

RISK

Why proxy_clear_logs is rated Critical

Irreversibly deletes logs without recovery mechanism; data loss cannot be undone.

From the tool's definition Clear all captured proxy request/response logs.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs proxy_clear_logs safely

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

proxy_clear_logs Hidden

proxy_clear_logs 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": [
    "proxy_clear_logs"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every proxy_clear_logs call is checked against it from then on.

FAQ

Questions about proxy_clear_logs

What does the proxy_clear_logs tool do? +

Clear all captured proxy request/response logs. It is categorised as a Destructive tool in the Jshookmcp 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 proxy_clear_logs? +

Register the Jshook MCP server in PolicyLayer and add a rule for proxy_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 Jshookmcp. Nothing to install.

What risk level is proxy_clear_logs? +

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

Yes. Add a rate_limit block to the proxy_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.

How do I block proxy_clear_logs completely? +

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

What MCP server provides proxy_clear_logs? +

proxy_clear_logs is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Jshook, and thousands of servers like it.

This server

All 736 Jshook tools → Critical-risk tools on this server →

Across the catalogue

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

Guides

Govern code and CI agents →Blast radius →Tool call approval →