GET /crl/latest.json when deployed; may 404 on minimal dev setups.
AI agents call kya_crl_latest to retrieve information from UMBRAXON/kya Hub without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves CRL (Certificate Revocation List) metadata without modifying any state. It performs a simple HTTP GET operation to fetch immutable data. The 404 possibility on minimal setups is a benign error condition, not a side effect. No write, execution, destructive, or financial operations are possible. Read-only data retrieval carries minimal risk.
From the tool's definition Tool name 'kya_crl_latest' and description indicate GET request to fetch '/crl/latest.json' (Certificate Revocation List metadata). Server description explicitly states 'Read-only MCP server' and lists CRL metadata retrieval as a core capability.
Attacks that exploit this kind of access
GET /crl/latest.json when deployed; may 404 on minimal dev setups. It is categorised as a Read tool in the UMBRAXON/kya Hub MCP Server, which means it retrieves data without modifying state.
Register the UMBRAXON/kya Hub MCP server in PolicyLayer and add a rule for kya_crl_latest: 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 UMBRAXON/kya Hub. Nothing to install.
kya_crl_latest 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 kya_crl_latest 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 kya_crl_latest. 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.
kya_crl_latest is provided by the UMBRAXON/kya Hub MCP server (umbraxon/kya-hub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →