AI agents use create_post to create or update resources in Hugo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hugo environment.
This tool creates new data (a post/content file) in a reversible manner. The effect is limited to adding a new file to the Hugo content directory, which can be undone by deleting the file. It does not execute arbitrary code, delete data, or move money, making it a Write-category action.
From the tool's definition Tool name 'create_post' explicitly indicates creation of new content. Description states 'Create a new Hugo post' which is a write operation that modifies the site structure by adding new content files.
Documented attack patterns abuse exactly the kind of access create_post 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 create_post:
{
"version": "1",
"default": "deny",
"tools": {
"create_post": {
"limits": [
{
"counter": "create_post_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_post stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new Hugo post. It is categorised as a Write tool in the Hugo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hugo MCP server in PolicyLayer and add a rule for create_post: 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.
create_post is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_post 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 create_post. 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.
create_post 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.