Extract tables from a document and return them as structured data
AI agents call extract_tables to retrieve information from MCP Docling Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries structured data (tables) from documents. It performs a read-only operation that does not modify, create, or delete data, and does not execute arbitrary code or commands. The blast radius of misuse is minimal—an agent could extract tables it shouldn't have access to, but cannot modify or delete content. This is classified as Read with low severity.
From the tool's definition Tool name: 'extract_tables' — 'Extract tables from a document and return them as structured data'. The description uses 'extract' and 'return', indicating data retrieval with no modification, creation, deletion, or execution of code. No side effects.
Documented attack patterns abuse exactly the kind of access extract_tables gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Docling Server, and nothing reaches the server without passing your rules. This is the rule we recommend for extract_tables:
{
"version": "1",
"default": "deny",
"tools": {
"extract_tables": {}
}
}extract_tables is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Extract tables from a document and return them as structured data. It is categorised as a Read tool in the MCP Docling Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Docling Server MCP server in PolicyLayer and add a rule for extract_tables: 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 MCP Docling Server. Nothing to install.
extract_tables 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 extract_tables 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 extract_tables. 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.
extract_tables is provided by the MCP Docling Server MCP server (zanetworker/mcp-docling). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Docling Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 MCP Docling Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.