AI agents call list_content to retrieve information from Hugo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool lists or queries existing content without creating, modifying, deleting, or executing operations. This is a passive information-gathering action typical of Read category tools. The low severity reflects minimal blast radius if misused by an AI agent—it can only expose information about the site structure and content.
From the tool's definition Tool name 'list_content' and description 'List content in the Hugo site' indicate a retrieval/query operation with no side effects.
Documented attack patterns abuse exactly the kind of access list_content gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Hugo, and nothing reaches the server without passing your rules. This is the rule we recommend for list_content:
{
"version": "1",
"default": "deny",
"tools": {
"list_content": {}
}
}list_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.
List content in the Hugo site. It is categorised as a Read tool in the Hugo MCP Server, which means it retrieves data without modifying state.
Register the Hugo MCP server in PolicyLayer and add a rule for list_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 Hugo. Nothing to install.
list_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 list_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 list_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.
list_content is provided by the Hugo MCP server (sunnycloudyang/hugo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Hugo, 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.
15 Hugo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.