Display a multi-field form to collect multiple inputs at once. All field values are stored in userContext using field keys. Use get_user_input to retrieve submitted values.
AI agents use show_multi_form to create or update resources in Pane — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pane environment.
This tool writes/stores user input data into persistent userContext state. It creates a UI form and persists the submitted values, which is a reversible write operation. It does not execute code, delete data, or involve financial transactions.
From the tool's definition Display a multi-field form to collect multiple inputs at once. All field values are stored in userContext using field keys.
Documented attack patterns abuse exactly the kind of access show_multi_form gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pane, and nothing reaches the server without passing your rules. This is the rule we recommend for show_multi_form:
{
"version": "1",
"default": "deny",
"tools": {
"show_multi_form": {
"limits": [
{
"counter": "show_multi_form_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}show_multi_form stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Display a multi-field form to collect multiple inputs at once. All field values are stored in userContext using field keys. Use get_user_input to retrieve submitted values. It is categorised as a Write tool in the Pane MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pane MCP server in PolicyLayer and add a rule for show_multi_form: 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 Pane. Nothing to install.
show_multi_form is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the show_multi_form 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 show_multi_form. 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.
show_multi_form is provided by the Pane MCP server (zabaca/pane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pane, 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.
15 Pane tools catalogued and risk-classified — across an index of 43,000+ MCP servers.