security-readiness — $0.02 USDC x402. POST https://conc-exe.xyz/api/concierge-security-readiness
AI agents call security_readiness 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.
Security readiness checks are informational assessments that read and report on existing security state without triggering side effects. While it uses POST (which can mutate), the function name and context (intel service, low cost, sibling tools like 'intel_desk_brief') indicate this retrieves readiness metrics or status rather than modifying systems.
From the tool's definition Tool name 'security_readiness' and description indicate a query/assessment function that retrieves or reports on security status.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
security-readiness — $0.02 USDC x402. POST https://conc-exe.xyz/api/concierge-security-readiness. It is categorised as a Read tool in the Concierge Intel MCP Server, which means it retrieves data without modifying state.
security_readiness 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_readiness: 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_readiness 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_readiness 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_readiness. 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_readiness 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_readiness 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 →