find_documents_by_content
AI agents call find_documents_by_content 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 tool name and context strongly suggest this performs a search or query of existing documents filtered by content, which is a read operation with no side effects. No data is modified or deleted. The empty description reduces confidence slightly, but the naming convention and placement among primarily write-heavy sibling tools supports classification as Read.
From the tool's definition Tool name 'find_documents_by_content' indicates a search/query operation that retrieves documents based on content matching. Sibling tools include write operations (create_*, add_*) and the name pattern 'find_' is consistent with read-only retrieval.
Attacks that exploit this kind of access
find_documents_by_content. 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 find_documents_by_content: 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.
find_documents_by_content 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 find_documents_by_content 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 find_documents_by_content. 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.
find_documents_by_content 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 →