get_document_activity
Use this to surface engagement signals for a single document when the GP wants to know which LPs are actually reading it. Returns per-viewer timestamps, view durations, and IPs.
This record as markdown: /tools/8vdx1-fundos-mcp/get-document-activity.md
What get_document_activity does on Fundos
AI agents call get_document_activity 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.
Why get_document_activity is rated Low
This tool retrieves and queries existing VDR engagement metadata (timestamps, view durations, IP addresses) for analytics purposes. It performs no data modification, deletion, or financial operations.
From the tool's definition Tool description: 'surface engagement signals for a single document...which LPs are actually reading it. Returns per-viewer timestamps, view durations, and IPs.' Keywords: 'returns' (retrieval only), no create/modify/delete operations.
Attacks that exploit this kind of access
The rule that runs get_document_activity 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_activity, this is the rule to start with:
get_document_activity 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 Fundos, apply this rule, and every get_document_activity call is checked against it from then on.
Questions about get_document_activity
Use this to surface engagement signals for a single document when the GP wants to know which LPs are actually reading it. Returns per-viewer timestamps, view durations, and IPs. It is categorised as a Read tool in the Fundos MCP Server, which means it retrieves data without modifying state.
Register the Fundos MCP server in PolicyLayer and add a rule for get_document_activity: 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.
get_document_activity 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_activity 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_activity. 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_activity 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.
More on Fundos, and thousands of servers like it.
This server
Across the catalogue