document_search
A read tool on the ContextForge MCP Gateway MCP server.
This record as markdown: /tools/jrmatherly-mcp-context-forge/document-search.md
What document_search does on ContextForge MCP Gateway
AI agents call document_search to retrieve information from ContextForge MCP Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why document_search is rated Low
The name 'document_search' strongly implies retrieval of documents or data without side effects. Although the description is empty (reducing confidence), the naming convention and context of sibling tools that perform write operations (add_*) clearly indicate this tool queries/retrieves data. No capability to create, modify, delete, execute code, or commit financial transactions is evident.
From the tool's definition Tool name 'document_search' indicates a search/query operation. Tool description is empty, limiting certainty.
Attacks that exploit this kind of access
The rule that runs document_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ContextForge MCP Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For document_search, this is the rule to start with:
document_search 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 ContextForge MCP Gateway, apply this rule, and every document_search call is checked against it from then on.
Questions about document_search
document_search is a read tool on the ContextForge MCP Gateway MCP server. It is categorised as a Read tool in the ContextForge MCP Gateway MCP Server, which means it retrieves data without modifying state.
Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for document_search: 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 ContextForge MCP Gateway. Nothing to install.
document_search 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 document_search 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 document_search. 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.
document_search is provided by the ContextForge MCP Gateway MCP server (jrmatherly/mcp-context-forge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ContextForge MCP Gateway, and thousands of servers like it.
This server
Across the catalogue