alertservice_create
Create a new alert notification service. Configures how and where alerts are delivered.
This record as markdown: /tools/nasbridge/alertservice-create.md
What alertservice_create does on Nasbridge
AI agents use alertservice_create 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 alertservice_create is rated Medium
This is a write operation that creates a new alert service configuration. It modifies system state by adding a notification service, but does not execute code, delete data, or move money.
From the tool's definition Tool name 'alertservice_create' and description states 'Create a new alert notification service. Configures how and where alerts are delivered.' The action is a CREATE operation that adds a new configuration record.
Attacks that exploit this kind of access
The rule that runs alertservice_create 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 alertservice_create, this is the rule to start with:
alertservice_create 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 alertservice_create call is checked against it from then on.
Questions about alertservice_create
Create a new alert notification service. Configures how and where alerts are delivered. 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 alertservice_create: 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.
alertservice_create 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 alertservice_create 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 alertservice_create. 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.
alertservice_create 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