microCMSについての質問に答える場合に利用します。ドキュメントから指定されたファイルを検索し、中身を返します。カテゴリーを指定することで特定のサブディレクトリのみを対象にできます。\n\nまだ
AI agents call search_document to retrieve information from microCMS Document MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries documentation content. It has no capability to modify, delete, or execute code. The ability to filter by category narrows scope but does not change the read-only nature. Appropriate for a documentation server where the primary function is information retrieval.
From the tool's definition Tool description states it "searches" documents and "returns" content from specified files. The Japanese description confirms: "searches for specified files from documents and returns the contents." Operations are: search, retrieve, return — all read-only…
Documented attack patterns abuse exactly the kind of access search_document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and microCMS Document MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_document:
{
"version": "1",
"default": "deny",
"tools": {
"search_document": {}
}
}search_document is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
microCMSについての質問に答える場合に利用します。ドキュメントから指定されたファイルを検索し、中身を返します。カテゴリーを指定することで特定のサブディレクトリのみを対象にできます。\n\nまだ. It is categorised as a Read tool in the microCMS Document MCP Server MCP Server, which means it retrieves data without modifying state.
Register the microCMS Document MCP Server MCP server in PolicyLayer and add a rule for search_document: 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 microCMS Document MCP Server. Nothing to install.
search_document 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 search_document 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 search_document. 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.
search_document is provided by the microCMS Document MCP Server MCP server (microcmsio/microcms-document-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from microCMS Document MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 microCMS Document MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.