security-headers — $0.02 USDC x402. POST https://conc-exe.xyz/api/concierge-security-headers
AI agents call security_headers to retrieve information from Concierge Intel without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | object | — | JSON POST body |
paymentSignature | string | — | Base64 PAYMENT-SIGNATURE header after x402 settlement |
Parameters from the server's own tool schema.
This tool retrieves security header information from a target endpoint. While POST is used, the semantics are read-only: it returns data about existing security configurations without side effects. The modest cost ($0.02 USDC) further indicates a lightweight query rather than a complex operation. No evidence of writes, destructive actions, or code execution.
From the tool's definition Tool name 'security_headers' and description indicate it queries security headers via HTTP POST, returning metadata about a target's security configuration.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
security-headers — $0.02 USDC x402. POST https://conc-exe.xyz/api/concierge-security-headers. It is categorised as a Read tool in the Concierge Intel MCP Server, which means it retrieves data without modifying state.
security_headers accepts 2 parameters: body, paymentSignature. The full parameter table on this page comes from the server's own tool schema.
Register the Concierge Intel MCP server in PolicyLayer and add a rule for security_headers: 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 Concierge Intel. Nothing to install.
security_headers 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_headers 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_headers. 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_headers is provided by the Concierge Intel MCP server (https://conc-exe.xyz/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
security_headers is one line of Concierge Intel's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →