crypto
Crypto: TLS/SSL audit, GPG, LUKS, file hashing, certificate lifecycle
This record as markdown: /tools/defense/crypto.md
What crypto does on Defense
AI agents invoke crypto to trigger actions in Defense. 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 |
|---|---|---|---|
host | string | — | Target hostname or IP |
name | string | — | LUKS mapper name |
path | string | — | File or directory path to hash |
port | number | — | Target port |
action | string | Yes | Action to perform |
device | string | — | Block device path, e.g. /dev/sda2 |
domain | string | — | Domain name for certificate checks |
key_id | string | — | GPG key ID |
dry_run | boolean | — | Preview without executing |
service | string | — | Service to audit TLS config for |
algorithm | string | — | Hash algorithm |
cert_path | string | — | Local certificate file path |
Parameters from the server's own tool schema.
Why crypto is rated High
This tool executes cryptographic operations and audits across multiple subsystems. Managing LUKS encryption can irreversibly affect disk access; GPG key management and certificate lifecycle operations can alter system trust stores; TLS/SSL auditing runs active probes.
From the tool's definition TLS/SSL audit, GPG, LUKS, file hashing, certificate lifecycle — implies running cryptographic operations, auditing TLS/SSL configurations, managing GPG keys, and handling LUKS disk encryption
Risk signalsAccepts file system path (file_path) · Accepts URL/endpoint input (host) · High parameter count (20 properties)
Attacks that exploit this kind of access
The rule that runs crypto safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Defense, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crypto, this is the rule to start with:
crypto 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 Defense, apply this rule, and every crypto call is checked against it from then on.
Questions about crypto
Crypto: TLS/SSL audit, GPG, LUKS, file hashing, certificate lifecycle. It is categorised as a Execute tool in the Defense MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
crypto accepts 12 parameters: host, name, path, port, action, device, domain, key_id, dry_run, service, algorithm, cert_path. Required: action. The full parameter table on this page comes from the server's own tool schema.
Register the Defense MCP server in PolicyLayer and add a rule for crypto: 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 Defense. Nothing to install.
crypto 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 crypto 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 crypto. 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.
crypto is provided by the Defense MCP server (defense-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Defense, and thousands of servers like it.
Across the catalogue