certificates_import
Run certificates.import through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/certificates-import.md
What certificates_import does on Appaloft
AI agents use certificates_import to create or update resources in Appaloft, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Appaloft environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
passphrase | string | — | |
privateKey | string | Yes | |
causationId | string | — | |
idempotencyKey | string | — | |
domainBindingId | string | Yes | |
certificateChain | string | Yes |
Parameters from the server's own tool schema.
Why certificates_import is rated Medium
Importing certificates modifies system security configuration by adding new certificates, which is a Write operation (creates/modifies data reversibly). Severity is high because certificate mismanagement could compromise TLS/SSL security, authentication, or authorization mechanisms if an AI agent imports malicious or misconfigured certificates.
From the tool's definition Tool name 'certificates_import' and description 'Run certificates.import through the Appaloft application operation catalog' indicate a data modification operation that imports certificates into the system.
Attacks that exploit this kind of access
The rule that runs certificates_import safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For certificates_import, this is the rule to start with:
certificates_import 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 Appaloft, apply this rule, and every certificates_import call is checked against it from then on.
Questions about certificates_import
Run certificates.import through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Write tool in the Appaloft MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
certificates_import accepts 6 parameters: passphrase, privateKey, causationId, idempotencyKey, domainBindingId, certificateChain. Required: privateKey, domainBindingId, certificateChain. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for certificates_import: 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 Appaloft. Nothing to install.
certificates_import 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 certificates_import 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 certificates_import. 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.
certificates_import is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appaloft, and thousands of servers like it.
This server
Across the catalogue