certificate_create
Create a new certificate. Supports internal (self-signed), CSR, imported, and ACME certificate types. Only name and create_type are required; other fields depend on the create_type.
This record as markdown: /tools/nasbridge/certificate-create.md
What certificate_create does on Nasbridge
AI agents use certificate_create to create or update resources in Nasbridge, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nasbridge environment.
Why certificate_create is rated Medium
This is fundamentally a Write operation—it creates and persists a new certificate object in TrueNAS with no permanent destructive capability. While certificates are security-sensitive, the tool itself is reversible (certificates can typically be deleted/replaced), and the operation doesn't execute arbitrary code, destroy existing data, or move money.
From the tool's definition Tool description states it will 'Create a new certificate', indicating a write operation that creates a new configuration artifact in the system.
Attacks that exploit this kind of access
The rule that runs certificate_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nasbridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For certificate_create, this is the rule to start with:
certificate_create 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 Nasbridge, apply this rule, and every certificate_create call is checked against it from then on.
Questions about certificate_create
Create a new certificate. Supports internal (self-signed), CSR, imported, and ACME certificate types. Only name and create_type are required; other fields depend on the create_type. It is categorised as a Write tool in the Nasbridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nasbridge MCP server in PolicyLayer and add a rule for certificate_create: 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 Nasbridge. Nothing to install.
certificate_create 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 certificate_create 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 certificate_create. 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.
certificate_create is provided by the Nasbridge MCP server (maverick0628/nasbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nasbridge, and thousands of servers like it.
This server
Across the catalogue