getDocument
Get a document by ID, including title, content, metadata, and file info.
This record as markdown: /tools/io-github-homenshum-nodebench/getdocument.md
What getDocument does on Nodebench
AI agents call getDocument to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getDocument is rated Low
This tool retrieves document information by ID and returns data. No modifications, deletions, or side effects are described. This is a straightforward data retrieval operation, classified as Read with low severity since retrieval of documents poses minimal risk even if misused by an AI agent.
From the tool's definition Tool description states 'Get a document by ID, including title, content, metadata, and file info.' The verb 'Get' and the retrieval nature of the operation indicate a read-only action that queries existing data without modification, creation, or deletion.
Attacks that exploit this kind of access
The rule that runs getDocument safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getDocument, this is the rule to start with:
getDocument 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 Nodebench, apply this rule, and every getDocument call is checked against it from then on.
Questions about getDocument
Get a document by ID, including title, content, metadata, and file info. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for getDocument: 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 Nodebench. Nothing to install.
getDocument 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 getDocument 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 getDocument. 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.
getDocument is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue