Send reminder notifications for specific invitations.
AI agents use send_reminder 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.
Sending reminders is a write-class operation that modifies the state of the system by creating notification records and triggering outbound communications. It is not destructive (notifications are not permanently irreversible in the data model), not financial, and not arbitrary code execution.
From the tool's definition Tool is named 'send_reminder' and described as 'Send reminder notifications for specific invitations.' This action creates or modifies state by sending notifications to invitation recipients, which is a reversible data creation action (notifications can be…
Attacks that exploit this kind of access
Send reminder notifications for specific invitations. 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 send_reminder: 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.
send_reminder 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 send_reminder 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 send_reminder. 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.
send_reminder 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 →