pgp_key_info
Inspect an OpenPGP public key (ASCII-armored or base64 binary) the way gpg --show-keys does, offline: primary key and subkey fingerprints and key IDs (v4, v5 and RFC 9580 v6 keys), algorithm and size / curve (RSA, DSA, ElGamal, ECDSA, ECDH, EdDSA, Ed25519 / Ed448, X25519 / X448), creation and exp...
This record as markdown: /tools/com-it-scorptech-x402/pgp-key-info.md
What pgp_key_info does on ScorpTech x402 API
AI agents call pgp_key_info 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 |
|---|---|---|---|
key | string | Yes | ASCII-armored public key block or base64 of the binary key |
now | integer | — | Unix time for expiry checks (default: now) |
Parameters from the server's own tool schema.
Why pgp_key_info is rated Low
Even though pgp_key_info 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.
Attacks that exploit this kind of access
The rule that runs pgp_key_info 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 pgp_key_info, this is the rule to start with:
pgp_key_info 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 pgp_key_info call is checked against it from then on.
Questions about pgp_key_info
Inspect an OpenPGP public key (ASCII-armored or base64 binary) the way gpg --show-keys does, offline: primary key and subkey fingerprints and key IDs (v4, v5 and RFC 9580 v6 keys), algorithm and size / curve (RSA, DSA, ElGamal, ECDSA, ECDH, EdDSA, Ed25519 / Ed448, X25519 / X448), creation and expiry from the self-signatures, revocations, capabilities (certify / sign / encrypt / authenticate), user IDs split into name / email / comment, preferred algorithms and features, the armor CRC-24 check and Web Key Directory (WKD) URLs for each email. Flags weak or deprecated keys, SHA-1 self-signatures, expired keys and keys without an encryption subkey. Private key blocks are refused. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/pgp-key-info. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
pgp_key_info accepts 2 parameters: key, now. Required: key. 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 pgp_key_info: 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.
pgp_key_info 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 pgp_key_info 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 pgp_key_info. 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.
pgp_key_info 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