Check your Lyrenth credit usage: plan tier, credits used against your
AI agents call check_usage to retrieve information from Lyrenth-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool inspects account metadata (usage statistics, plan tier) without modifying, executing, or deleting anything. It is a straightforward read operation that retrieves information for display or monitoring purposes. Low severity reflects minimal blast radius if misused—an AI agent can only view account status, not alter it.
From the tool's definition Tool name 'check_usage' and description indicate it retrieves credit/usage information: 'Check your Lyrenth credit usage: plan tier, credits used against your'. This is a query operation with no side effects.
Attacks that exploit this kind of access
Check your Lyrenth credit usage: plan tier, credits used against your. It is categorised as a Read tool in the Lyrenth-MCP MCP Server, which means it retrieves data without modifying state.
Register the Lyrenth- MCP server in PolicyLayer and add a rule for check_usage: 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 Lyrenth-MCP. Nothing to install.
check_usage 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_usage 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_usage. 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_usage is provided by the Lyrenth- MCP server (lyrenth-mcp). 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 →