order_ssl_certificate
Order a new SSL certificate from 20i
This record as markdown: /tools/cbrown35-20i-mcp/order-ssl-certificate.md
What order_ssl_certificate does on 20i MCP Server
AI agents use order_ssl_certificate to commit financial operations through 20i MCP Server, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why order_ssl_certificate is rated Critical
Ordering an SSL certificate from a hosting provider typically incurs a financial charge. This constitutes committing a financial obligation, placing it in the Financial category. Misuse could result in unwanted purchases billed to the account.
From the tool's definition 'Order a new SSL certificate from 20i' — ordering a certificate implies a purchase/financial transaction with the hosting provider.
Attacks that exploit this kind of access
The rule that runs order_ssl_certificate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 20i MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For order_ssl_certificate, this is the rule to start with:
Any call to order_ssl_certificate is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect 20i MCP Server, apply this rule, and every order_ssl_certificate call is checked against it from then on.
Questions about order_ssl_certificate
Order a new SSL certificate from 20i. It is categorised as a Financial tool in the 20i MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the 20i MCP Server MCP server in PolicyLayer and add a rule for order_ssl_certificate: 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 20i MCP Server. Nothing to install.
order_ssl_certificate is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the order_ssl_certificate 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 order_ssl_certificate. 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.
order_ssl_certificate is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 20i MCP Server, and thousands of servers like it.
Across the catalogue