Extract specific named fields from a document using Claude AI. Returns a JSON object with the requested field names as keys and extracted values as strings (null when a field is not found). Ideal for structured extraction from invoices, contracts, receipts, forms, etc. You can pass pre-extracted ...
Accepts URL/endpoint input (url); Accepts file system path (file_path)
Part of the Docpulse MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke parse_fields to trigger processes or run actions in Docpulse. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
parse_fields can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
parse_fields:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Docpulse policy for all 4 tools.
Agents calling execute-class tools like parse_fields have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
parse_fields is one of the high-risk operations in Docpulse. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Extract specific named fields from a document using Claude AI. Returns a JSON object with the requested field names as keys and extracted values as strings (null when a field is not found). Ideal for structured extraction from invoices, contracts, receipts, forms, etc. You can pass pre-extracted text via `text` or provide a document source.. It is categorised as a Execute tool in the Docpulse MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for parse_fields. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Docpulse MCP server.
parse_fields is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the parse_fields rule in your Intercept 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 Intercept policy for parse_fields. 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.
parse_fields is provided by the Docpulse MCP server (nicholasemccormick/docpulse-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.