# get_document_pipeline

Obtain the CivilQuants customer-side document pipeline — the toolkit the document-heavy skills (tender review, geotechnical / geo-environmental interpretation) use to chunk a tender pack and render a Word pack on the user's machine. Returns the self-unpacking chunking package, the pipeline discipline, and the python-docx render helpers. Universal (free + paid). NOTE: running the pipeline over real documents requires a code-execution client (Claude Code / Codex / VS Code) — a chat connector can read the toolkit but cannot execute it. The full kit is large (~60 KB); pass component='chunking'|'discipline'|'render' for one part (~20 KB each), or omit it for the whole kit.

Agent View of the PolicyLayer registry record for `get_document_pipeline`. HTML page: https://policylayer.com/tools/com-civilquants-civilquants/get-document-pipeline

## Facts

- Tool: `get_document_pipeline`
- Server: Civilquants (`https://api.civilquants.com/mcp`) — https://policylayer.com/tools/com-civilquants-civilquants.md
- Homepage: https://github.com/https://api.civilquants.com/mcp
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `component` | string | no | Which part to fetch; omit for the whole kit. |

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": "get_document_pipeline",
    "arguments": {}
  }
}
```

## Why get_document_pipeline is rated Low

This tool retrieves and provides access to a document processing pipeline toolkit. While the toolkit itself may be used for code execution elsewhere, the tool only reads/returns configuration and helper code without modifying data, executing arbitrary operations, or affecting user documents directly. The returned package requires external execution (Claude Code, VS Code) to have any effect.

From the tool's own definition: "Tool description states it 'Obtain[s]' and 'Returns' a toolkit/package - core verbs are about retrieval. Description explicitly notes 'a chat connector can read the toolkit but cannot execute it,' indicating the tool itself performs no execution or…"

## Use case

AI agents call get_document_pipeline to retrieve information from Civilquants without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_document_pipeline": {}
  }
}
```

## Other tools on Civilquants (55)

- `compute_box_culvert` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-box-culvert.md
- `compute_combined_services_trench` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-combined-services-trench.md
- `compute_connection_to_existing` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-connection-to-existing.md
- `compute_ditch` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-ditch.md
- `compute_embankment_cross_section` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-embankment-cross-section.md
- `compute_end_area_earthworks` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-end-area-earthworks.md
- `compute_gabion_wall` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-gabion-wall.md
- `compute_headwall_attenuation_outlet` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-headwall-attenuation-outlet.md
- `compute_highway_drainage_channel` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-highway-drainage-channel.md
- `compute_lighting_column` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-lighting-column.md
- `compute_multi_section_assembly` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-multi-section-assembly.md
- `compute_pad_foundation` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-pad-foundation.md
- `compute_parapet` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-parapet.md
- `compute_pipe_bedding` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-pipe-bedding.md
- `compute_reinforced_soil_wall` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-reinforced-soil-wall.md
- `compute_road_marking` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-road-marking.md
- `compute_single_service_run` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-single-service-run.md
- `compute_soakaway` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-soakaway.md
- `compute_soil_nailed_slope` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-soil-nailed-slope.md
- `compute_traffic_sign` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-traffic-sign.md
- `compute_utility_chamber` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-utility-chamber.md
- `compute_utility_kiosk_base` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/compute-utility-kiosk-base.md
- `recompute_project` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/recompute-project.md
- `render_skill_report` — Execute — https://policylayer.com/tools/com-civilquants-civilquants/render-skill-report.md
- `compute_attenuation_tank` — Read — https://policylayer.com/tools/com-civilquants-civilquants/compute-attenuation-tank.md
- `compute_bored_pile_wall` — Read — https://policylayer.com/tools/com-civilquants-civilquants/compute-bored-pile-wall.md
- `compute_cantilever_wall` — Read — https://policylayer.com/tools/com-civilquants-civilquants/compute-cantilever-wall.md
- `compute_carrier_pipe_run` — Read — https://policylayer.com/tools/com-civilquants-civilquants/compute-carrier-pipe-run.md
- `compute_catchpit` — Read — https://policylayer.com/tools/com-civilquants-civilquants/compute-catchpit.md
- `compute_edge_drain` — Read — https://policylayer.com/tools/com-civilquants-civilquants/compute-edge-drain.md
- …and 25 more: https://policylayer.com/tools/com-civilquants-civilquants.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=com-civilquants-civilquants · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-civilquants-civilquants