generate_docs · Musea MCP: Risk & Policy

WHAT IT DOES

What generate_docs does on Musea

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

WHY IT NEEDS A POLICY

Why generate_docs needs a policy

This tool generates markdown documentation, which is a reversible write operation - it creates new files or modifies documentation artifacts that can be edited, reverted, or deleted without permanent system damage. It has no execution capabilities (not Execute), does not delete data (not Destructive), and poses no financial risk. The blast radius is limited to documentation content, making it low severity.

From the tool's definition Tool name 'generate_docs' and description 'Generate Markdown documentation for a design-system component from its .art.vue definition' indicates the tool creates documentation files (new data artifacts).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_docs Rate-limited

generate_docs 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_docs": {
      "limits": [
        {
          "counter": "generate_docs_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 Musea, so you can run agents against it safely.

FAQ

Questions about generate_docs

What does the generate_docs tool do? +

Generate Markdown documentation for a design-system component from its .art.vue definition. It is categorised as a Write tool in the Musea 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_docs? +

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

What risk level is generate_docs? +

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

Can I rate-limit generate_docs? +

Yes. Add a rate_limit block to the generate_docs 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_docs completely? +

Set action: deny in the PolicyLayer policy for generate_docs. 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_docs? +

generate_docs is provided by the Musea MCP server (@vizejs/musea-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.