Create a new alert notification service. Configures how and where alerts are delivered.
AI agents use alertservice_create to create or update resources in Truenas — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Truenas environment.
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.
Documented attack patterns abuse exactly the kind of access alertservice_create gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Truenas, and nothing reaches the server without passing your rules. This is the rule we recommend for alertservice_create:
{
"version": "1",
"default": "deny",
"tools": {
"alertservice_create": {
"limits": [
{
"counter": "alertservice_create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Create a new alert notification service. Configures how and where alerts are delivered. It is categorised as a Write tool in the Truenas MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Truenas 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 Truenas. 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 Truenas MCP server (spranab/truenas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Truenas, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
279 Truenas tools catalogued and risk-classified — across an index of 43,000+ MCP servers.