get_document_metadata

Use this to inspect a single document

SERVERFundos SOURCE8vdx1/fundos-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/8vdx1-fundos-mcp/get-document-metadata.md

WHAT IT DOES

What get_document_metadata does on Fundos

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

RISK

Why get_document_metadata is rated Low

This tool queries document metadata within a VDR (Virtual Data Room) system without creating, modifying, deleting, or executing any operations. The action is informational and has no side effects on the document or fund data. In a fund management context, metadata inspection supports due diligence workflows but cannot alter state.

From the tool's definition Tool name 'get_document_metadata' and description 'inspect a single document' indicate retrieval of metadata without modification. The verb 'inspect' and 'get' are characteristic of read-only operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_document_metadata safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Fundos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_document_metadata, this is the rule to start with:

get_document_metadata Allowed

get_document_metadata is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_document_metadata": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Fundos, apply this rule, and every get_document_metadata call is checked against it from then on.

FAQ

Questions about get_document_metadata

What does the get_document_metadata tool do? +

Use this to inspect a single document. It is categorised as a Read tool in the Fundos MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_document_metadata? +

Register the Fundos 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 Fundos. Nothing to install.

What risk level is get_document_metadata? +

get_document_metadata is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_document_metadata? +

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.

How do I block get_document_metadata completely? +

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.

What MCP server provides get_document_metadata? +

get_document_metadata is provided by the Fundos MCP server (8vdx1/fundos-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Fundos, and thousands of servers like it.

This server

All 57 Fundos tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →