activate_license
Call this when the user runs /design-doc --activate KEY. Verifies the key against the backend and caches the result locally (with a 7-day offline grace period) so future runs don't need network access.
This record as markdown: /tools/design-doc-generator-mcp/activate-license.md
What activate_license does on Design Doc Generator
AI agents use activate_license to create or update resources in Design Doc Generator, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Design Doc Generator environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
key | string | Yes | The license key the user provided. |
Parameters from the server's own tool schema.
Why activate_license is rated Medium
The tool writes/caches a license key result locally and calls a backend to verify a license. This is a Write operation (creating/modifying local state). While license activation can have financial implications, the tool itself only verifies and caches a pre-purchased key rather than initiating a financial transaction or commitment, so Write is the most appropriate category.
From the tool's definition Verifies the key against the backend and caches the result locally
Attacks that exploit this kind of access
The rule that runs activate_license safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Design Doc Generator, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For activate_license, this is the rule to start with:
activate_license 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Design Doc Generator, apply this rule, and every activate_license call is checked against it from then on.
Questions about activate_license
Call this when the user runs /design-doc --activate KEY. Verifies the key against the backend and caches the result locally (with a 7-day offline grace period) so future runs don't need network access. It is categorised as a Write tool in the Design Doc Generator MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
activate_license accepts 1 parameter: key. Required: key. The full parameter table on this page comes from the server's own tool schema.
Register the Design Doc Generator MCP server in PolicyLayer and add a rule for activate_license: 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 Design Doc Generator. Nothing to install.
activate_license 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 activate_license 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 activate_license. 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.
activate_license is provided by the Design Doc Generator MCP server (design-doc-generator-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Design Doc Generator, and thousands of servers like it.
This server
Across the catalogue