get_credit_balance
Current credit balance + plan info. Check before expensive steps (a full segment render can cost hundreds of credits — generate_segments dry_run gives the estimate). Jobs covered by a BYOK provider key bill 0.
This record as markdown: /tools/com-framesail-framesail/get-credit-balance.md
What get_credit_balance does on Framesail
AI agents call get_credit_balance to retrieve information from Framesail without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_credit_balance is rated Low
This tool queries and returns existing data (credit balance and plan details) without modifying, executing operations, or affecting external systems. It is a read-only operation used for informational purposes before taking other actions. No destructive, financial transactions, or code execution occurs—only data retrieval.
From the tool's definition Tool name 'get_credit_balance' and description 'Current credit balance + plan info. Check before expensive steps' indicate retrieval of account/billing information with no side effects.
Attacks that exploit this kind of access
The rule that runs get_credit_balance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Framesail, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_credit_balance, this is the rule to start with:
get_credit_balance 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 Framesail, apply this rule, and every get_credit_balance call is checked against it from then on.
Questions about get_credit_balance
Current credit balance + plan info. Check before expensive steps (a full segment render can cost hundreds of credits — generate_segments dry_run gives the estimate). Jobs covered by a BYOK provider key bill 0. It is categorised as a Read tool in the Framesail MCP Server, which means it retrieves data without modifying state.
Register the Framesail MCP server in PolicyLayer and add a rule for get_credit_balance: 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 Framesail. Nothing to install.
get_credit_balance 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 get_credit_balance 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 get_credit_balance. 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.
get_credit_balance is provided by the Framesail MCP server (https://api.framesail.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Framesail, and thousands of servers like it.
This server
Across the catalogue