x509_decode
Decode PEM/DER X.509 certificates, chains and CSRs offline: subject/issuer DN, serial, validity and days left, SANs, key type/size/curve, signature algorithm, key usage / EKU / basic constraints, AKI/SKI, OCSP / CA-issuer / CRL URLs, policies and embedded SCT count, SHA-1/SHA-256 fingerprints and...
This record as markdown: /tools/com-it-scorptech-x402/x509-decode.md
What x509_decode does on ScorpTech x402 API
AI agents call x509_decode to retrieve information from ScorpTech x402 API without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
pem | string | Yes | One or more PEM certificates (leaf first) and/or a CSR, or base64 DER |
hostname | string | — | Optional hostname / IP to check against the leaf SANs |
Parameters from the server's own tool schema.
Why x509_decode is rated Low
Even though x509_decode only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts URL/endpoint input (hostname)
Attacks that exploit this kind of access
The rule that runs x509_decode safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For x509_decode, this is the rule to start with:
x509_decode is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every x509_decode call is checked against it from then on.
Questions about x509_decode
Decode PEM/DER X.509 certificates, chains and CSRs offline: subject/issuer DN, serial, validity and days left, SANs, key type/size/curve, signature algorithm, key usage / EKU / basic constraints, AKI/SKI, OCSP / CA-issuer / CRL URLs, policies and embedded SCT count, SHA-1/SHA-256 fingerprints and SPKI pin; verifies each chain link signature and order, flags self-signed, expired / expiring, weak keys, SHA-1 signatures and over-long lifetimes, and checks hostname coverage (RFC 6125 wildcards). Private keys are refused. Price: $0.003 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/x509-decode. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
x509_decode accepts 2 parameters: pem, hostname. Required: pem. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for x509_decode: 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 ScorpTech x402 API. Nothing to install.
x509_decode is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the x509_decode 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 x509_decode. 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.
x509_decode is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue