Read config, auth, capability, setup-web, media, saved cursor, and workspace state before using other fal tools.
AI agents call fal_status to retrieve information from Simple Fal 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 queries existing state and configuration information. It performs no writes, deletions, code execution, or financial transactions. It is a precursor/diagnostic tool used to inspect system state before other operations. The low severity reflects minimal blast radius—incorrect state reading might cause workflow issues but cannot directly damage data or execute arbitrary operations.
From the tool's definition Tool description explicitly states 'Read config, auth, capability, setup-web, media, saved cursor, and workspace state'.
Attacks that exploit this kind of access
Read config, auth, capability, setup-web, media, saved cursor, and workspace state before using other fal tools. It is categorised as a Read tool in the Simple Fal MCP Server, which means it retrieves data without modifying state.
Register the Simple Fal MCP server in PolicyLayer and add a rule for fal_status: 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 Simple Fal. Nothing to install.
fal_status 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 fal_status 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 fal_status. 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.
fal_status is provided by the Simple Fal MCP server (pintar-team/simple-fal-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 →