Submit a response to a form.
AI agents use submit_form to create or update resources in Nettskjema MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nettskjema MCP Server environment.
The tool creates new submission records in the Nettskjema system. While submissions are data additions, they are not irreversible (delete_submissions exists as a sibling tool) and do not execute arbitrary code or trigger external side effects beyond form data recording. This fits the Write category.
From the tool's definition Tool description states 'Submit a response to a form' — this creates/adds new form submission data that can be modified or removed later (as evidenced by sibling tool delete_submissions), making it a reversible write operation rather than destructive.
Attacks that exploit this kind of access
Submit a response to a form. It is categorised as a Write tool in the Nettskjema MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nettskjema MCP Server MCP server in PolicyLayer and add a rule for submit_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 Nettskjema MCP Server. Nothing to install.
submit_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 submit_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 submit_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.
submit_form is provided by the Nettskjema MCP Server MCP server (orjahren/nettskjema-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 →