get_form
Read one of your forms to verify it is wired correctly: returns its access_key, destination_email, destination_verified (whether submissions will be emailed yet), allowed_domains, and notification/autoresponder/webhook config. Never returns the webhook signing secret. Errors with: unauthorized, n...
This record as markdown: /tools/com-formpaste-formpaste/get-form.md
What get_form does on Formpaste
AI agents call get_form to retrieve information from Formpaste without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
formId | string | Yes | A form id from create_form or list_forms, e.g. frm_... |
Parameters from the server's own tool schema.
Why get_form is rated Low
This tool retrieves and queries form configuration metadata without side effects. It does not create, modify, delete, or execute operations. The explicit exclusion of the webhook signing secret further demonstrates a read-only posture.
From the tool's definition Tool description states 'Read one of your forms' and 'returns' configuration details (access_key, destination_email, allowed_domains, webhook config).
Attacks that exploit this kind of access
The rule that runs get_form safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Formpaste, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_form, this is the rule to start with:
get_form is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Formpaste, apply this rule, and every get_form call is checked against it from then on.
Questions about get_form
Read one of your forms to verify it is wired correctly: returns its access_key, destination_email, destination_verified (whether submissions will be emailed yet), allowed_domains, and notification/autoresponder/webhook config. Never returns the webhook signing secret. Errors with: unauthorized, not_found. It is categorised as a Read tool in the Formpaste MCP Server, which means it retrieves data without modifying state.
get_form accepts 1 parameter: formId. Required: formId. The full parameter table on this page comes from the server's own tool schema.
Register the Formpaste MCP server in PolicyLayer and add a rule for get_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 Formpaste. Nothing to install.
get_form 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_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 get_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.
get_form is provided by the Formpaste MCP server (formpaste-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Formpaste, and thousands of servers like it.
This server
Across the catalogue