Check your Meshy account credit balance. Returns the current number of credits available in your account. Args: - response_format (enum): Output format -
AI agents call meshy_check_balance to retrieve information from Meshy MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and returns the current credit balance from the user's Meshy account. It performs no modifications, deletions, financial transactions, or external operations—purely a read operation. The severity is low because exposure of this tool to an AI agent poses minimal risk; checking a balance cannot cause damage beyond potential information disclosure.
From the tool's definition Tool name 'meshy_check_balance' and description 'Check your Meshy account credit balance' and 'Returns the current number of credits available in your account' indicate a query operation that retrieves account information without modification or side effects.
Documented attack patterns abuse exactly the kind of access meshy_check_balance gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Meshy MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for meshy_check_balance:
{
"version": "1",
"default": "deny",
"tools": {
"meshy_check_balance": {}
}
} meshy_check_balance is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check your Meshy account credit balance. Returns the current number of credits available in your account. Args: - response_format (enum): Output format -. It is categorised as a Read tool in the Meshy MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Meshy MCP Server MCP server in PolicyLayer and add a rule for meshy_check_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 Meshy MCP Server. Nothing to install.
meshy_check_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 meshy_check_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 meshy_check_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.
meshy_check_balance is provided by the Meshy MCP Server MCP server (meshy-dev/meshy-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Meshy MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 Meshy MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.