# edit_document

Edit a document by replacing a string in the documents content with a new string.

Agent View of the PolicyLayer registry record for `edit_document`. HTML page: https://policylayer.com/tools/abdullah-1121-mcp-2/edit-document

## Facts

- Tool: `edit_document`
- Server: MCP Chat (`abdullah-1121/mcp-2`) — https://policylayer.com/tools/abdullah-1121-mcp-2.md
- Homepage: https://github.com/Abdullah-1121/MCP-2
- Risk category: Write (Medium risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "edit_document",
    "arguments": {}
  }
}
```

## Why edit_document is rated Medium

The tool modifies document content through string replacement, which is a reversible write operation. While documents could theoretically contain critical data, the operation itself is not destructive (data is replaced, not deleted) and is categorized as Write.

From the tool's own definition: "Tool description explicitly states 'Edit a document by replacing a string in the documents content with a new string.' This is a direct modification operation that creates or modifies data reversibly."

## Use case

AI agents use edit_document to create or update resources in MCP Chat, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Chat environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches MCP Chat:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "edit_document": {
      "limits": [
        {
          "counter": "edit_document_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on MCP Chat (7)

- `order_pizza` — Financial — https://policylayer.com/tools/abdullah-1121-mcp-2/order-pizza.md
- `process_item` — Other — https://policylayer.com/tools/abdullah-1121-mcp-2/process-item.md
- `analyze_project` — Read — https://policylayer.com/tools/abdullah-1121-mcp-2/analyze-project.md
- `download_file` — Read — https://policylayer.com/tools/abdullah-1121-mcp-2/download-file.md
- `process_data` — Read — https://policylayer.com/tools/abdullah-1121-mcp-2/process-data.md
- `read_doc_contents` — Read — https://policylayer.com/tools/abdullah-1121-mcp-2/read-doc-contents.md
- `create_story` — Write — https://policylayer.com/tools/abdullah-1121-mcp-2/create-story.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=abdullah-1121-mcp-2 · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/abdullah-1121-mcp-2