Recommend the best static site generator based on project analysis and user preferences
AI agents call recommend_ssg to retrieve information from Documcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool analyzes project metadata and provides recommendations. It retrieves or queries data (project analysis) and returns suggestions without creating, modifying, deleting, or executing external operations. The output is informational guidance only, making it a Read operation with low severity and blast radius.
From the tool's definition Tool name is 'recommend_ssg' and description states it 'recommend[s] the best static site generator based on project analysis and user preferences' — a pure analysis and recommendation operation with no data modification, deletion, or external execution.
Documented attack patterns abuse exactly the kind of access recommend_ssg gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Documcp, and nothing reaches the server without passing your rules. This is the rule we recommend for recommend_ssg:
{
"version": "1",
"default": "deny",
"tools": {
"recommend_ssg": {}
}
}recommend_ssg 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.
Recommend the best static site generator based on project analysis and user preferences. It is categorised as a Read tool in the Documcp MCP Server, which means it retrieves data without modifying state.
Register the Docu MCP server in PolicyLayer and add a rule for recommend_ssg: 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 Documcp. Nothing to install.
recommend_ssg 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 recommend_ssg 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 recommend_ssg. 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.
recommend_ssg is provided by the Docu MCP server (tosin2013/documcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Documcp, 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.
52 Documcp tools catalogued and risk-classified — across an index of 43,000+ MCP servers.