Get document metadata and structure with chunk navigation from a specific folder
AI agents call get_document_metadata to retrieve information from Folder without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata and structural information about documents without modifying or executing anything. It is a read-only operation that queries file system properties and document structure, consistent with the Read category for data retrieval with no side effects.
From the tool's definition Tool name 'get_document_metadata' and description 'Get document metadata and structure' indicate retrieval of file information. The server description emphasizes 'read...local file systems' and 'provides tools for listing files...reading file contents'.
Documented attack patterns abuse exactly the kind of access get_document_metadata gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Folder, and nothing reaches the server without passing your rules. This is the rule we recommend for get_document_metadata:
{
"version": "1",
"default": "deny",
"tools": {
"get_document_metadata": {}
}
}get_document_metadata 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.
Get document metadata and structure with chunk navigation from a specific folder. It is categorised as a Read tool in the Folder MCP Server, which means it retrieves data without modifying state.
Register the Folder MCP server in PolicyLayer and add a rule for get_document_metadata: 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 Folder. Nothing to install.
get_document_metadata 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_metadata 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_metadata. 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_metadata is provided by the Folder MCP server (okets/folder-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Folder, 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.
9 Folder tools catalogued and risk-classified — across an index of 43,000+ MCP servers.