security_txt
Fetch and validate a site's security.txt (RFC 9116) for vulnerability disclosure: tries /.well-known/security.txt then the legacy /security.txt (SSRF-safe), parses Contact / Expires / Encryption / Policy / Acknowledgments / Preferred-Languages / Canonical / Hiring / CSAF, handles PGP-signed files...
This record as markdown: /tools/com-it-scorptech-x402/security-txt.md
What security_txt does on ScorpTech x402 API
AI agents call security_txt 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 |
|---|---|---|---|
domain | string | Yes | Domain or URL of the site |
Parameters from the server's own tool schema.
Why security_txt is rated Low
Even though security_txt 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 security_txt 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 security_txt, this is the rule to start with:
security_txt 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 security_txt call is checked against it from then on.
Questions about security_txt
Fetch and validate a site's security.txt (RFC 9116) for vulnerability disclosure: tries /.well-known/security.txt then the legacy /security.txt (SSRF-safe), parses Contact / Expires / Encryption / Policy / Acknowledgments / Preferred-Languages / Canonical / Hiring / CSAF, handles PGP-signed files, and reports RFC errors (missing or expired Expires, non-URI contacts, wrong content type, http links, Canonical mismatch) with days until expiry. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/security-txt. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
security_txt accepts 1 parameter: domain. Required: domain. 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 security_txt: 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.
security_txt 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 security_txt 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 security_txt. 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.
security_txt 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