GET /api/tiers — tier list and pricing metadata.
AI agents call kya_tiers 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 fetches tier and pricing information from the UMBRAXON KYA-Hub API without modifying, deleting, or executing any operations. It is a straightforward data retrieval endpoint with no irreversible effects, code execution, or financial transactions. The low severity reflects minimal risk even if called inappropriately by an agent.
From the tool's definition Tool name 'kya_tiers' and description 'GET /api/tiers — tier list and pricing metadata' indicate a read-only retrieval operation. The HTTP verb GET and the server's stated purpose as 'Read-only MCP server' confirm no side effects.
Attacks that exploit this kind of access
GET /api/tiers — tier list and pricing metadata. 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_tiers: 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_tiers 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_tiers 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_tiers. 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_tiers 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 →