Check the Rendex account: which plan it's on, how many render credits have been used vs. the monthly limit (and when it resets), the per-minute rate limit, and a one-tap link to upgrade to a higher tier. Use this whenever the user asks about their usage, remaining quota, current plan, or how to g...
AI agents call rendex_account to retrieve information from Rendex Screenshot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely retrieves and queries account metadata without side effects. It returns usage statistics, plan information, and rate limits—all read operations. The explicit 'Read-only' declaration and emphasis on no credit cost confirm it has no destructive, executable, or modifying capabilities. Low severity because misuse would only expose account information, not enable harmful actions.
From the tool's definition Tool description states 'Read-only — costs no credits' and explicitly describes retrieving account information: 'which plan it's on, how many render credits have been used vs.
Attacks that exploit this kind of access
Check the Rendex account: which plan it's on, how many render credits have been used vs. the monthly limit (and when it resets), the per-minute rate limit, and a one-tap link to upgrade to a higher tier. Use this whenever the user asks about their usage, remaining quota, current plan, or how to get more renders / stop hitting limits. Read-only — costs no credits. It is categorised as a Read tool in the Rendex Screenshot MCP Server, which means it retrieves data without modifying state.
Register the Rendex Screenshot MCP server in PolicyLayer and add a rule for rendex_account: 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 Rendex Screenshot. Nothing to install.
rendex_account 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 rendex_account 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 rendex_account. 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.
rendex_account is provided by the Rendex Screenshot MCP server (copperline-labs/rendex-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
rendex_account is one line of Rendex Screenshot's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →