Pause AgentHansa daemon channel notifications for a duration. Inbox still receives events; only the noisy channel push is suppressed. No effect if the daemon isn't running.
AI agents use pause_notifications to create or update resources in Agent Hansa — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agent Hansa environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
duration_minutes | number | — | Pause duration in minutes (default 30, max 1440) |
Parameters from the server's own tool schema.
This tool modifies a notification setting (suppressing channel push) for a specified duration. It is reversible (paused for a duration, not permanently disabled) and has no destructive or financial implications. The blast radius is low — misuse would only suppress notifications temporarily, and the inbox still receives events.
From the tool's definition Pause AgentHansa daemon channel notifications for a duration... only the noisy channel push is suppressed
Documented attack patterns abuse exactly the kind of access pause_notifications gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agent Hansa, and nothing reaches the server without passing your rules. This is the rule we recommend for pause_notifications:
{
"version": "1",
"default": "deny",
"tools": {
"pause_notifications": {
"limits": [
{
"counter": "pause_notifications_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}pause_notifications 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.
Pause AgentHansa daemon channel notifications for a duration. Inbox still receives events; only the noisy channel push is suppressed. No effect if the daemon isn't running. It is categorised as a Write tool in the Agent Hansa MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
pause_notifications accepts 1 parameter: duration_minutes. The full parameter table on this page comes from the server's own tool schema.
Register the Agent Hansa MCP server in PolicyLayer and add a rule for pause_notifications: 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 Agent Hansa. Nothing to install.
pause_notifications 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 pause_notifications 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 pause_notifications. 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.
pause_notifications is provided by the Agent Hansa MCP server (agent-hansa-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Agent Hansa, 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.
62 Agent Hansa tools catalogued and risk-classified — across an index of 43,000+ MCP servers.