Semantic search across all manuscript content
AI agents call search_content to retrieve information from Claude Writer's Aid MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs content retrieval and analysis only. Searching manuscript content is a read-only operation with no side effects, no code execution, no data modification, and no destructive capability. The low severity reflects minimal blast radius even if misused — an AI agent using this tool cannot damage data, leak sensitive information at scale, or trigger external operations.
From the tool's definition Semantic search across all manuscript content — described as a search operation that retrieves and queries data without modifying or executing external operations.
Documented attack patterns abuse exactly the kind of access search_content gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Writer's Aid MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for search_content:
{
"version": "1",
"default": "deny",
"tools": {
"search_content": {}
}
} search_content 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.
Semantic search across all manuscript content. It is categorised as a Read tool in the Claude Writer's Aid MCP MCP Server, which means it retrieves data without modifying state.
Register the Claude Writer's Aid MCP server in PolicyLayer and add a rule for search_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 Claude Writer's Aid MCP. Nothing to install.
search_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 search_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 search_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.
search_content is provided by the Claude Writer's Aid MCP server (xiaolai/claude-writers-aid-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Writer's Aid MCP, 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.
34 Claude Writer's Aid MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.