AI agents call delete_finding to permanently remove resources in Reptor — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Despite the empty description, the tool name 'delete_finding' unambiguously indicates a destructive operation. Deleting findings in a pentest report system irreversibly removes data and assessment records. This is more severe than Write (which is reversible) or Execute (which depends on arguments).
From the tool's definition Tool name is 'delete_finding' with an empty description. The verb 'delete' indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access delete_finding gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Reptor, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_finding:
{
"version": "1",
"default": "deny",
"hide": [
"delete_finding"
]
}delete_finding disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
delete_finding. It is categorised as a Destructive tool in the Reptor MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Reptor MCP server in PolicyLayer and add a rule for delete_finding: 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 Reptor. Nothing to install.
delete_finding 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 delete_finding 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 delete_finding. 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.
delete_finding is provided by the Reptor MCP server (slvnlrt/reptor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Reptor, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Reptor tools catalogued and risk-classified — across an index of 43,000+ MCP servers.