Skip to main content
Glama
runtimeguard

runtime-guard

Official

write_file

Create or modify files with controlled access, preventing unauthorized writes to sensitive paths through runtime security checks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
contentYes
ctxNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler implementation for the `write_file` tool, including policy checks, cumulative budget tracking, automatic backups, and the actual file writing operation.
    def write_file(path: str, content: 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="write_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)
    
            budget_fields: dict = {}
            if result.allowed:
                budget_allowed, budget_reason, budget_rule, budget_fields = check_and_record_cumulative_budget(
                    tool="write_file",
                    command=None,
                    affected_paths=[path],
                    operation_count=1,
                    bytes_estimate=len(content.encode()),
                )
                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("write_file", result, path=path, **budget_fields)
            append_log_entry(log_entry)
            if not result.allowed:
                return f"[POLICY BLOCK] {result.reason}"
    
            backup_location = None
            backup_enabled = bool(POLICY.get("audit", {}).get("backup_enabled", True))
            if backup_enabled and os.path.exists(path):
                backup_location = backup_paths([path])
                if backup_location:
                    append_log_entry(
                        {
                            **log_entry,
                            "source": "mcp-server",
                            "backup_location": backup_location,
                            "event": "backup_created",
                        }
                    )
    
            try:
                with open(path, "w") as f:
                    f.write(content)
            except OSError as e:
                return f"Error writing file: {e}"
    
            msg = f"Successfully wrote {len(content)} characters to {path}"
            if backup_location:
                msg += f" (previous version backed up to {backup_location})"
            else:
                msg += " (no content-change backup needed)"
            return msg
        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/runtime-guard'

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