# style_paragraph

Applies paragraph formatting to every paragraph overlapping [start_index, end_index): named_style (normal_text, title, subtitle, heading_1..heading_6 — the way to make headings), alignment (start/center/end/justified), line_spacing (100 = single, 200 = double), space_above/space_below (points), indent_start/indent_end/indent_first_line (points), keep_with_next and direction (ltr/rtl). Only the provided fields change; at least one is required. A range inside a single paragraph styles that whole paragraph.

Agent View of the PolicyLayer registry record for `style_paragraph`. HTML page: https://policylayer.com/tools/a1-x-tech-mcp-google-docs/style-paragraph

## Facts

- Tool: `style_paragraph`
- Server: Mcp Google Docs (`@a1-x-tech/mcp-google-docs`) — https://policylayer.com/tools/a1-x-tech-mcp-google-docs.md
- Install: `npx -y @a1-x-tech/mcp-google-docs`
- Homepage: https://github.com/A1-x-Tech/mcp-google-docs
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 12 (3 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `tab_id` | string | no | Tab to target (from list_tabs). Omit for the first/only tab. |
| `alignment` | string | no | Text alignment. |
| `direction` | string | no | Content direction. |
| `end_index` | integer | yes | End of the paragraph range (exclusive). |
| `indent_end` | number | no | Indent from the end edge, points. |
| `segment_id` | string | no | Header/footer/footnote segment id (from get_document). Omit for the document body. |
| `document_id` | string | yes | The document id — the long id from the document URL (docs.google.com/document/d/<documentId>/edit) or from create_document output. |
| `named_style` | string | no | Named paragraph style — headings feed the document outline. |
| `space_above` | number | no | Extra space above the paragraph, points. |
| `space_below` | number | no | Extra space below the paragraph, points. |
| `start_index` | integer | yes | Start of the paragraph range (inclusive). |
| `indent_start` | number | no | Indent from the start edge, points. |

Parameters from the server's own tool schema.

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "style_paragraph",
    "arguments": {
      "end_index": 0,
      "document_id": "<document_id>",
      "start_index": 0
    }
  }
}
```

## Why style_paragraph is rated High

style_paragraph triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Risk signals: High parameter count (15 properties)

## Use case

AI agents invoke style_paragraph to trigger actions in Mcp Google Docs. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "style_paragraph": {
      "limits": [
        {
          "counter": "style_paragraph_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Mcp Google Docs (26)

- `delete_range` — Destructive — https://policylayer.com/tools/a1-x-tech-mcp-google-docs/delete-range.md
- `logout` — Destructive — https://policylayer.com/tools/a1-x-tech-mcp-google-docs/logout.md
- `manage_comment` — Destructive — https://policylayer.com/tools/a1-x-tech-mcp-google-docs/manage-comment.md
- `start_login` — Execute — https://policylayer.com/tools/a1-x-tech-mcp-google-docs/start-login.md
- `auth_status` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-docs/auth-status.md
- `get_document` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-docs/get-document.md
- `list_comments` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-docs/list-comments.md
- `list_tabs` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-docs/list-tabs.md
- `raw_request` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-docs/raw-request.md
- `read_document_text` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-docs/read-document-text.md
- `style_text` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-docs/style-text.md
- `create_document` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-docs/create-document.md
- `edit_table` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-docs/edit-table.md
- `export_document` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-docs/export-document.md
- `finish_login` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-docs/finish-login.md
- `import_markdown` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-docs/import-markdown.md
- `insert_break` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-docs/insert-break.md
- `insert_image` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-docs/insert-image.md
- `insert_table` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-docs/insert-table.md
- `insert_text` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-docs/insert-text.md
- `replace_all_text` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-docs/replace-all-text.md
- `replace_image` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-docs/replace-image.md
- `replace_range` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-docs/replace-range.md
- `set_client` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-docs/set-client.md
- `set_paragraph_bullets` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-docs/set-paragraph-bullets.md
- `setup_instructions` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-docs/setup-instructions.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=a1-x-tech-mcp-google-docs · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/a1-x-tech-mcp-google-docs