certificates_issue_or_renew
Run certificates.issue-or-renew through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/certificates-issue-or-renew.md
What certificates_issue_or_renew does on Appaloft
AI agents invoke certificates_issue_or_renew to trigger actions in Appaloft. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
reason | string | — | |
causationId | string | — | |
providerKey | string | — | |
certificateId | string | — | |
challengeType | string | — | |
idempotencyKey | string | — | |
domainBindingId | string | Yes |
Parameters from the server's own tool schema.
Why certificates_issue_or_renew is rated High
The tool executes an operation to issue or renew TLS/SSL certificates, triggering an external PKI operation. This is an Execute-category action as it runs an operation with real-world effects (certificate issuance/renewal) rather than simply reading or writing data. Severity is high because misuse could cause certificate churn, service disruptions, or exhaust certificate quota limits.
From the tool's definition 'Run certificates.issue-or-renew through the Appaloft application operation catalog'
Attacks that exploit this kind of access
The rule that runs certificates_issue_or_renew 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_issue_or_renew, this is the rule to start with:
certificates_issue_or_renew stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_issue_or_renew call is checked against it from then on.
Questions about certificates_issue_or_renew
Run certificates.issue-or-renew through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Execute tool in the Appaloft MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
certificates_issue_or_renew accepts 7 parameters: reason, causationId, providerKey, certificateId, challengeType, idempotencyKey, domainBindingId. Required: domainBindingId. 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_issue_or_renew: 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_issue_or_renew is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the certificates_issue_or_renew 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_issue_or_renew. 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_issue_or_renew 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.
Across the catalogue