Create and assign a domain to an app (includes SSL setup)
AI agents use faber_create_domain to create or update resources in Faber MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Faber MCP Server environment.
This tool creates new DNS/domain records and provisions SSL certificates, both of which are write operations that modify live infrastructure. While not destructive (the domain could theoretically be removed later), the scope and blast radius are significant — misconfigured domains or SSL could break application accessibility or security.
From the tool's definition Tool description states it will 'Create and assign a domain to an app (includes SSL setup)' — these are irreversible operations that modify infrastructure configuration.
Attacks that exploit this kind of access
Create and assign a domain to an app (includes SSL setup). It is categorised as a Write tool in the Faber MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Faber MCP Server MCP server in PolicyLayer and add a rule for faber_create_domain: 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 Faber MCP Server. Nothing to install.
faber_create_domain 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 faber_create_domain 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 faber_create_domain. 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.
faber_create_domain is provided by the Faber MCP Server MCP server (joshtrebilco/faber-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 →