Skip to main content
Glama

delete_file

Remove files from your system with policy enforcement. The ai-runtime-guard server validates deletion requests against configured security rules before execution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
ctxNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The implementation of the delete_file tool, which includes path policy checking, budget verification, backup creation, and file deletion.
    def delete_file(path: str, ctx: Context | None = None) -> str:
        context_tokens = activate_runtime_context(ctx)
        path = str(pathlib.Path(WORKSPACE_ROOT) / path) if not os.path.isabs(path) else path
    
        try:
            path_check = check_path_policy(path, tool="delete_file")
            if path_check:
                result = PolicyResult(allowed=False, reason=path_check[0], decision_tier="blocked", matched_rule=path_check[1])
            else:
                result = PolicyResult(allowed=True, reason="allowed", decision_tier="allowed", matched_rule=None)
    
            if result.allowed:
                if not os.path.exists(path):
                    append_log_entry(build_log_entry("delete_file", result, path=path, error="file not found"))
                    return f"Error: file not found: {path}"
    
                if os.path.isdir(path):
                    result = PolicyResult(
                        allowed=False,
                        reason=f"'{path}' is a directory  -  delete_file only removes individual files. Use execute_command for directory operations (note: bulk/recursive deletions are also subject to policy).",
                        decision_tier="blocked",
                        matched_rule=None,
                    )
    
            budget_fields: dict = {}
            if result.allowed:
                bytes_est = 0
                try:
                    if os.path.isfile(path):
                        bytes_est = int(os.path.getsize(path))
                except OSError:
                    bytes_est = 0
                budget_allowed, budget_reason, budget_rule, budget_fields = check_and_record_cumulative_budget(
                    tool="delete_file",
                    command=None,
                    affected_paths=[path],
                    operation_count=1,
                    bytes_estimate=bytes_est,
                )
                if not budget_allowed:
                    result = PolicyResult(
                        allowed=False,
                        reason=budget_reason or "Cumulative blast-radius budget exceeded for current scope.",
                        decision_tier="blocked",
                        matched_rule=budget_rule or "requires_simulation.cumulative_budget_exceeded",
                    )
    
            log_entry = build_log_entry("delete_file", result, path=path, **budget_fields)
            if not result.allowed:
                append_log_entry(log_entry)
                return f"[POLICY BLOCK] {result.reason}"
    
            backup_enabled = bool(POLICY.get("audit", {}).get("backup_enabled", True))
            backup_location = backup_paths([path]) if backup_enabled else ""
            if backup_location:
                log_entry["backup_location"] = backup_location
    
            append_log_entry(log_entry)
    
            try:
                os.remove(path)
            except OSError as e:
                return f"Error deleting file: {e}"
    
            return f"Successfully deleted {path}. " + (
                f"Backup saved to {backup_location}  -  the file can be recovered from there."
                if backup_location
                else "No content-change backup was needed."
            )
        finally:
            reset_runtime_context(context_tokens)
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/runtimeguard/ai-runtime-guard'

If you have feedback or need assistance with the MCP directory API, please join our Discord server