This record as markdown: /tools/kiln/check-my-tier.md
What check_my_tier does on Kiln
AI agents call check_my_tier to retrieve information from Kiln without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_my_tier is rated Low
This tool appears to retrieve account or licensing tier information without modifying any state. While the empty description reduces confidence, the naming convention strongly suggests a read operation. Classified as Read with low severity due to minimal blast radius if misused (at worst, unauthorized visibility of account status).
From the tool's definition Tool name 'check_my_tier' suggests a read-only query of user account or subscription status. No description provided, but the verb 'check' and absence of modification language indicate a retrieval operation.
Attacks that exploit this kind of access
The rule that runs check_my_tier safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Kiln, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_my_tier, this is the rule to start with:
check_my_tier is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Kiln, apply this rule, and every check_my_tier call is checked against it from then on.
Questions about check_my_tier
check_my_tier is a read tool on the Kiln MCP server. It is categorised as a Read tool in the Kiln MCP Server, which means it retrieves data without modifying state.
Register the Kiln MCP server in PolicyLayer and add a rule for check_my_tier: 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 Kiln. Nothing to install.
check_my_tier 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 check_my_tier 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 check_my_tier. 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.
check_my_tier is provided by the Kiln MCP server (codeofaxel/Kiln). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Kiln, and thousands of servers like it.
This server
Across the catalogue