AI agents call get-models-builder-status to retrieve information from Mcp Dev without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a simple status check operation characteristic of Read operations. It retrieves information about the Models Builder state without any side effects, modifications, or execution of arbitrary code. The blast radius of misuse is minimal—an attacker could only learn about the current compilation status of generated models, which is non-sensitive metadata.
From the tool's definition Tool description: 'Gets the out-of-date status of Models Builder models. Returns an object containing status...' This is a retrieval operation that queries the state of Models Builder models without modifying, executing, or deleting any data.
Attacks that exploit this kind of access
Gets the out-of-date status of Models Builder models. Returns an object containing: - status: The out-of-date status, one of:. It is categorised as a Read tool in the Mcp Dev MCP Server, which means it retrieves data without modifying state.
Register the Mcp Dev MCP server in PolicyLayer and add a rule for get-models-builder-status: 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.
get-models-builder-status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get-models-builder-status 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 get-models-builder-status. 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.
get-models-builder-status 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 →