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 discip...
This record as markdown: /tools/com-civilquants-civilquants/get-document-pipeline.md
What get_document_pipeline does on Civilquants
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
component | string | — | Which part to fetch; omit for the whole kit. |
Parameters from the server's own tool schema.
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 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…
Attacks that exploit this kind of access
The rule that runs get_document_pipeline safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Civilquants, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_document_pipeline, this is the rule to start with:
get_document_pipeline is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Civilquants, apply this rule, and every get_document_pipeline call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Civilquants MCP Server, which means it retrieves data without modifying state.
get_document_pipeline accepts 1 parameter: component. The full parameter table on this page comes from the server's own tool schema.
Register the Civilquants MCP server in PolicyLayer and add a rule for get_document_pipeline: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Civilquants. Nothing to install.
get_document_pipeline is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_document_pipeline rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for get_document_pipeline. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
get_document_pipeline is provided by the Civilquants MCP server (https://api.civilquants.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Civilquants, and thousands of servers like it.
This server
Across the catalogue