mail_update
Update mail/SMTP configuration for system email alerts. All fields are optional — only provide the ones you want to change.
This record as markdown: /tools/nasbridge/mail-update.md
What mail_update does on Nasbridge
AI agents use mail_update to create or update resources in Nasbridge, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nasbridge environment.
Why mail_update is rated Medium
This tool creates or modifies SMTP/mail configuration settings reversibly. While it affects system behavior (email alert delivery), the changes are not destructive and can be reverted by updating the configuration again. The severity is medium because misconfiguration could disrupt critical system notifications, but no data is deleted and no external financial transactions are involved.
From the tool's definition Tool name 'mail_update' and description explicitly states 'Update mail/SMTP configuration' — this modifies system email settings.
Attacks that exploit this kind of access
The rule that runs mail_update safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nasbridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mail_update, this is the rule to start with:
mail_update 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Nasbridge, apply this rule, and every mail_update call is checked against it from then on.
Questions about mail_update
Update mail/SMTP configuration for system email alerts. All fields are optional — only provide the ones you want to change. It is categorised as a Write tool in the Nasbridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nasbridge MCP server in PolicyLayer and add a rule for mail_update: 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 Nasbridge. Nothing to install.
mail_update 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 mail_update 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 mail_update. 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.
mail_update is provided by the Nasbridge MCP server (maverick0628/nasbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nasbridge, and thousands of servers like it.
This server
Across the catalogue