Delete specific submissions from a form.
AI agents call delete_submissions to permanently remove resources in Nettskjema MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes form submission data, which cannot be undone. Deletion of user-submitted data is an irreversible action with significant blast radius—an AI agent with access could wipe out critical survey responses, application submissions, or other form data.
From the tool's definition Tool name is 'delete_submissions' and description states 'Delete specific submissions from a form.' The verb 'delete' combined with 'submissions' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete specific submissions from a form. It is categorised as a Destructive tool in the Nettskjema MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Nettskjema MCP Server MCP server in PolicyLayer and add a rule for delete_submissions: 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.
delete_submissions is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_submissions 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 delete_submissions. 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.
delete_submissions 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 →