GET /api/cert/{kya_id}
AI agents call kya_cert 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 queries and retrieves certificate information by ID with no modification, creation, deletion, or execution of external operations. It is a straightforward read operation with no side effects. The read-only nature of the server and the GET HTTP method confirm this classification. Severity is low because retrieval of certificate metadata poses minimal risk of misuse by an AI agent.
From the tool's definition Tool description states 'GET /api/cert/{kya_id}' — a GET request that retrieves certificate data. Server is explicitly described as 'Read-only MCP server' with tools to 'fetch tiers/health, certificates, reputation, CRL metadata, and to verify' payloads.
Attacks that exploit this kind of access
GET /api/cert/{kya_id}. 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_cert: 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_cert 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_cert 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_cert. 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_cert 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 →