Control the local setup panel on demand. Use status to inspect it, start to open it, and stop to close it.
AI agents invoke fal_setup_web 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.
The tool controls a local setup panel by starting or stopping it, which constitutes executing external operations/processes rather than simply reading or writing data. The blast radius is medium since it affects local UI state and potentially configuration workflows, but does not directly delete data or move money.
From the tool's definition 'start to open it, and stop to close it' — triggers external operations (opening/closing a local setup panel UI process)
Attacks that exploit this kind of access
Control the local setup panel on demand. Use status to inspect it, start to open it, and stop to close it. 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_setup_web: 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_setup_web 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_setup_web 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_setup_web. 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_setup_web 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 →