GET /api/cert/{kya_id}/status
AI agents call kya_cert_status 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 performs data retrieval only (GET endpoint) from a read-only MCP server. It queries certificate metadata/status without modifying, executing, or deleting any data. The read-only nature of the server and the GET HTTP method indicate no capability for side effects. Severity is low as certificate status information is typically non-sensitive operational data with minimal blast radius if misused.
From the tool's definition Tool is described as a GET request to fetch certificate status by ID. The description explicitly states the server is 'Read-only' and this tool retrieves status data with 'no side effects'.
Attacks that exploit this kind of access
GET /api/cert/{kya_id}/status. 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_status: 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_status 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_status 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_status. 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_status 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 →