Use after fal_run to wait on a queue request, check status, fetch the final result, retry local downloads, cancel a request, or inspect saved request history.
AI agents invoke fal_request to trigger actions in Simple Fal. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool performs multiple operations including canceling requests (a state-changing action) and fetching results from external services. While much of it is read-oriented (status checks, fetching results), the ability to cancel a running request is an irreversible external operation. The tool spans Read and Execute categories; cancel operations tip it to Execute as the most severe applicable category.
From the tool's definition wait on a queue request, check status, fetch the final result, retry local downloads, cancel a request, or inspect saved request history
Attacks that exploit this kind of access
Use after fal_run to wait on a queue request, check status, fetch the final result, retry local downloads, cancel a request, or inspect saved request history. It is categorised as a Execute tool in the Simple Fal MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Simple Fal MCP server in PolicyLayer and add a rule for fal_request: 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_request is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the fal_request 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_request. 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_request 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 →