Returns an agentic readiness card for a provider or x402 resource. Answers four questions before an agent pays: - can_spend: bool — is it safe to spend on this resource? - trust_score: 0-100 — composite trust signal - proof: dict — V5 receipt path, known wallets, on-chain anchors - caveats: list[...
Part of the TWZRD Agent Intelligence server.
Free to start. No card required.
AI agents call get_readiness_card_tool to retrieve information from TWZRD Agent Intelligence without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_readiness_card_tool only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_readiness_card_tool": {}
}
}See the full TWZRD Agent Intelligence policy for all 8 tools.
These attack patterns abuse exactly the kind of access get_readiness_card_tool gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Returns an agentic readiness card for a provider or x402 resource. Answers four questions before an agent pays: - can_spend: bool — is it safe to spend on this resource? - trust_score: 0-100 — composite trust signal - proof: dict — V5 receipt path, known wallets, on-chain anchors - caveats: list[str] — risk factors and negative signals - next_fixes: list[str] — what the provider should fix to improve trust - decision: "allow" | "warn" | "block" - trust_score_basis: str — ALWAYS a free heuristic from the small internal registry + Dexter marketplace signals (dexter_heuristic_registry_v0:*). This is NOT the real 42k+ cross-facilitator x402 corpus. The full corpus (x402_payment_receipts + intel_renorm_v1 + signed V5 receipt) is paid-only, via GET /v1/intel/trust/{wallet}. A caveat always restates this. Provide at least one of resource_name or seller_wallet.. It is categorised as a Read tool in the TWZRD Agent Intelligence MCP Server, which means it retrieves data without modifying state.
Register the TWZRD Agent Intelligence MCP server in PolicyLayer and add a rule for get_readiness_card_tool: 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 TWZRD Agent Intelligence. Nothing to install.
get_readiness_card_tool 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 get_readiness_card_tool 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 get_readiness_card_tool. 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.
get_readiness_card_tool is provided by the TWZRD Agent Intelligence MCP server (twzrd-sol/wzrd-final). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 TWZRD Agent Intelligence tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.