util_security_txt_inspect
Find security.txt contacts, disclosure policy, and trust links for a domain.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/util-security-txt-inspect.md
What util_security_txt_inspect does on Delx Mcp A2a
AI agents call util_security_txt_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 | Origin or URL to inspect |
timeout | integer | — | Timeout in seconds (1-15) |
Parameters from the server's own tool schema.
Why util_security_txt_inspect is rated Low
This tool performs read-only inspection of security.txt configuration files on domains. It retrieves existing public metadata (contacts, policies, trust information) without modifying, executing code, or causing side effects. The action is informational and non-destructive, fitting the Read category with low severity due to minimal blast radius from misuse.
From the tool's definition Tool name and description indicate data retrieval: 'inspect' and 'Find security.txt contacts, disclosure policy, and trust links' — querying publicly available security metadata from a domain's security.txt file.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs util_security_txt_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_security_txt_inspect, this is the rule to start with:
util_security_txt_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_security_txt_inspect call is checked against it from then on.
Questions about util_security_txt_inspect
Find security.txt contacts, disclosure policy, and trust links for a domain. It is categorised as a Read tool in the Delx Mcp A2a MCP Server, which means it retrieves data without modifying state.
util_security_txt_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_security_txt_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_security_txt_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_security_txt_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_security_txt_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_security_txt_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