generate_documents · DocAgent MCP: Risk & Policy

WHAT IT DOES

What generate_documents does on DocAgent

AI agents use generate_documents to create or update resources in DocAgent — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DocAgent environment.

WHY IT NEEDS A POLICY

Why generate_documents needs a policy

The tool creates new document artifacts without destructive capability. While the output is reversible (documents can be edited or deleted), the primary action is content generation/creation, which is a Write operation. The severity is low because the blast radius of generating unwanted documentation is minimal—documents can be easily discarded without affecting production systems or data integrity.

From the tool's definition Tool name 'generate_documents' and description 'Generate specific documents' indicate document creation functionality. The server context confirms this is a documentation generation suite that 'creates comprehensive software documentation.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_documents Rate-limited

generate_documents 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_documents": {
      "limits": [
        {
          "counter": "generate_documents_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches DocAgent, so you can run agents against it safely.

FAQ

Questions about generate_documents

What does the generate_documents tool do? +

Generate specific documents. It is categorised as a Write tool in the DocAgent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on generate_documents? +

Register the DocAgent MCP server in PolicyLayer and add a rule for generate_documents: 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 DocAgent. Nothing to install.

What risk level is generate_documents? +

generate_documents is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit generate_documents? +

Yes. Add a rate_limit block to the generate_documents 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.

How do I block generate_documents completely? +

Set action: deny in the PolicyLayer policy for generate_documents. 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.

What MCP server provides generate_documents? +

generate_documents is provided by the DocAgent MCP server (vinnyfds/docagent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.