util_tls_inspect
Inspect TLS issuer, subject, SANs, and expiry to check trust and renewal risk.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/util-tls-inspect.md
What util_tls_inspect does on Delx Mcp A2a
AI agents call util_tls_inspect to retrieve information from Delx Mcp A2a 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 |
|---|---|---|---|
url | string | Yes | HTTPS URL or hostname to inspect |
timeout | integer | — | Timeout in seconds (1-15) |
Parameters from the server's own tool schema.
Why util_tls_inspect is rated Low
This tool retrieves and examines certificate metadata to assess security posture and renewal risk. It performs no mutations, executes no code, and triggers no external operations. While TLS inspection could inform decisions about critical infrastructure, the tool itself only reads certificate data without acting on it, making it a low-severity Read operation.
From the tool's definition Tool inspects TLS certificate properties (issuer, subject, SANs, expiry) — purely observational actions with no modification, execution, or side effects. The verb 'inspect' and the focus on checking trust properties confirm read-only behavior.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs util_tls_inspect safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Mcp A2a, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For util_tls_inspect, this is the rule to start with:
util_tls_inspect 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 Delx Mcp A2a, apply this rule, and every util_tls_inspect call is checked against it from then on.
Questions about util_tls_inspect
Inspect TLS issuer, subject, SANs, and expiry to check trust and renewal risk. It is categorised as a Read tool in the Delx Mcp A2a MCP Server, which means it retrieves data without modifying state.
util_tls_inspect accepts 2 parameters: url, timeout. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Mcp A2a MCP server in PolicyLayer and add a rule for util_tls_inspect: 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 Delx Mcp A2a. Nothing to install.
util_tls_inspect 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 util_tls_inspect 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 util_tls_inspect. 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.
util_tls_inspect is provided by the Delx Mcp A2a MCP server (https://api.delx.ai/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Mcp A2a, and thousands of servers like it.
This server
Across the catalogue