Delete old runs with optional manifest preservation. Supports age-based and count-based retention policies.
AI agents call indexfoundry_run_cleanup to permanently remove resources in IndexFoundry MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool's primary function is irreversible deletion of old runs. Age-based and count-based retention policies determine what gets deleted, but the deletion itself cannot be undone. The optional manifest preservation does not change the destructive nature of the core operation. Misuse by an AI agent (e.g., with aggressive retention settings) could result in loss of significant indexed data and pipeline history.
From the tool's definition "Delete old runs with optional manifest preservation" — the tool explicitly deletes runs, with deletion being the primary action. While manifests can optionally be preserved, the underlying run data is irreversibly removed.
Attacks that exploit this kind of access
Delete old runs with optional manifest preservation. Supports age-based and count-based retention policies. It is categorised as a Destructive tool in the IndexFoundry MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the IndexFoundry MCP server in PolicyLayer and add a rule for indexfoundry_run_cleanup: 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 IndexFoundry MCP. Nothing to install.
indexfoundry_run_cleanup 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 indexfoundry_run_cleanup 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 indexfoundry_run_cleanup. 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.
indexfoundry_run_cleanup is provided by the IndexFoundry MCP server (mnehmos/mnehmos.index-foundry.mcp). 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 →