get_documents
AI agents call get_documents to retrieve information from RSpace MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix is a strong signal for read-only data retrieval. No side effects are implied. The absence of a detailed description lowers confidence slightly, but the naming convention and server context (accessing RSpace data) make it clear this queries existing documents rather than modifying, executing, or deleting them. Low severity due to read-only nature with minimal blast radius.
From the tool's definition Tool name 'get_documents' with standard 'get' prefix indicates a retrieval operation. Context of sibling tools (create_*, add_*) and server description mentioning 'access and manipulate research data' confirms this retrieves existing research documents from…
Attacks that exploit this kind of access
get_documents. It is categorised as a Read tool in the RSpace MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RSpace MCP Server MCP server in PolicyLayer and add a rule for get_documents: 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 RSpace MCP Server. Nothing to install.
get_documents 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_documents 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_documents. 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_documents is provided by the RSpace MCP Server MCP server (rspace-os/rspace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →