AI agents use create_host_and_enrollment_code to create or update resources in Defined — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Defined environment.
This tool creates new infrastructure resources (hosts and enrollment codes) in a Defined Networking environment. Creation of hosts and credentials is reversible (hosts can be deleted, codes revoked), placing it in Write rather than Execute or Destructive. However, the inability to verify exact parameters and the high potential impact on network infrastructure if misused by an agent warrant 'high' severity.
From the tool's definition Tool name 'create_host_and_enrollment_code' indicates creation of infrastructure objects. Sibling tools include 'create_host', 'create_network', 'create_role', and 'create_enrollment_code', which are all Write operations.
Attacks that exploit this kind of access
create_host_and_enrollment_code. It is categorised as a Write tool in the Defined MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Defined MCP server in PolicyLayer and add a rule for create_host_and_enrollment_code: 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 Defined. Nothing to install.
create_host_and_enrollment_code 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 create_host_and_enrollment_code 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 create_host_and_enrollment_code. 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.
create_host_and_enrollment_code is provided by the Defined MCP server (quickvm/defined-mcp). 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 →