Triggers the generation/build of Models Builder models. This endpoint initiates the process of generating strongly-typed models from Umbraco content types. The operation runs asynchronously and does not return any response data. Use this tool to: - Generate models after making changes to document...
AI agents invoke post-models-builder-build to trigger actions in Mcp Dev. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers a build/code-generation process on the server, which executes an external operation (model generation from content types). It does not simply read or write data, but runs a background process that generates code files. Misuse could cause unintended model regeneration, potentially breaking a running application if content types are inconsistent, making it Execute with medium severity.
From the tool's definition Triggers the generation/build of Models Builder models... initiates the process of generating strongly-typed models... runs asynchronously
Attacks that exploit this kind of access
Triggers the generation/build of Models Builder models. This endpoint initiates the process of generating strongly-typed models from Umbraco content types. The operation runs asynchronously and does not return any response data. Use this tool to: - Generate models after making changes to document types, media types, or member types - Refresh models when they become out of date - Ensure the latest content type definitions are reflected in generated models Note: This operation may take some time to complete depending on the number of content types. Use get-models-builder-dashboard or get-models-builder-status to check the current state and if new models need to be generated. It is categorised as a Execute tool in the Mcp Dev MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Dev MCP server in PolicyLayer and add a rule for post-models-builder-build: 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 Mcp Dev. Nothing to install.
post-models-builder-build is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the post-models-builder-build 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 post-models-builder-build. 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.
post-models-builder-build is provided by the Mcp Dev MCP server (@umbraco-cms/mcp-dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →