Generate configuration files for the selected static site generator
AI agents use generate_config to create or update resources in Documcp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Documcp environment.
The tool creates or modifies configuration files, which is a reversible write operation. While configuration files are important for system behavior, they can be edited or deleted afterwards, making this Write rather than Execute or Destructive.
From the tool's definition Tool description states it will 'Generate configuration files' - this explicitly creates new files/configuration data.
Documented attack patterns abuse exactly the kind of access generate_config 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 generate_config:
{
"version": "1",
"default": "deny",
"tools": {
"generate_config": {
"limits": [
{
"counter": "generate_config_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}generate_config 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.
Generate configuration files for the selected static site generator. It is categorised as a Write tool in the Documcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Docu MCP server in PolicyLayer and add a rule for generate_config: 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.
generate_config 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 generate_config 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 generate_config. 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.
generate_config 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.