Get usage and spending history for your Fal.ai workspace. Shows quantity, cost, and breakdown by model. Requires admin API key.
AI agents call get_usage to retrieve information from Fal Ai MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a Read operation as it retrieves usage and spending history without making any modifications. However, severity is elevated to 'medium' rather than 'low' because the data retrieved is financially sensitive (spending history, costs by model) and requires admin API key access.
From the tool's definition Tool name 'get_usage' and description 'Get usage and spending history' indicate data retrieval with 'no side effects'. The tool 'Shows quantity, cost, and breakdown by model' confirms it queries historical data rather than modifying it.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access get_usage gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Fal Ai MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_usage:
{
"version": "1",
"default": "deny",
"tools": {
"get_usage": {}
}
}get_usage 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.
Get usage and spending history for your Fal.ai workspace. Shows quantity, cost, and breakdown by model. Requires admin API key. It is categorised as a Read tool in the Fal Ai MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Fal Ai MCP Server MCP server in PolicyLayer and add a rule for get_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 Fal Ai MCP Server. Nothing to install.
get_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 get_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 get_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.
get_usage is provided by the Fal Ai MCP Server MCP server (luminarylane/fal-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 18 Fal Ai MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
18 Fal Ai MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.