Check if Hugo is installed and get its version
AI agents call check_hugo_installation 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.
This is a passive information retrieval operation that queries the system state to determine Hugo's installation status and version. It has no capacity to modify, execute, delete, or create resources. The blast radius of misuse is minimal—an agent cannot cause harm by repeatedly checking Hugo's installation status.
From the tool's definition Tool performs a check/inspection operation ('Check if Hugo is installed and get its version') with no modifications or side effects. It retrieves version information about an installed tool.
Documented attack patterns abuse exactly the kind of access check_hugo_installation 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 check_hugo_installation:
{
"version": "1",
"default": "deny",
"tools": {
"check_hugo_installation": {}
}
}check_hugo_installation 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.
Check if Hugo is installed and get its version. 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 check_hugo_installation: 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.
check_hugo_installation 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 check_hugo_installation 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 check_hugo_installation. 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.
check_hugo_installation 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.